WordPress 5.7 Development Cycle

n

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

Matt Mullenweg is the Release lead, Tonya Mork is the Triage Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the Core Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the Accessibility Lead, Tim Hengeveld is the Design Lead,  JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release lead, Tonya Mork is the Triage Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the Core Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the Accessibility Lead, Tim Hengeveld is the Design Lead,  JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

n

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field Guide | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release lead, Tonya Mork is the Triage Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the Core Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the Accessibility Lead, Tim Hengeveld is the Design Lead,  JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field Guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7

WordPress 5.7 will be the first major release of 2021.

Matt Mullenweg is the Release lead The community member ultimately responsible for the Release., Tonya Mork is the Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the Accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,  JB Audras is the Docs Lead, and Monika Rao the Test Lead.

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.

Release Schedule

17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook.

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next at Wednesday at 05:00 UTC and Wednesday at 20:00 UTC.

Wish us luck!

n

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field Guide | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release lead, Tonya Mork is the Triage Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the Core Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the Accessibility Lead, Tim Hengeveld is the Design Lead,  JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notes and About page, and last chance to merge feature projects. (Slack archive, Zip download)nnnn
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.nnnn
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release datennnn

To get involved in WordPress core development, head over to Trac, and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #core Slack channel, which occur next at [time relative]Wednesday at 05:00 UTC[/time] and [time relative]Wednesday at 20:00 UTC[/time]. nnnn

Wish us luck!n“,”contentFiltered”:”

Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 5.7nnnn

WordPress 5.7 will be the first major release of 2021. nnnn

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both u201cdirect accessu201d (i.e. unassisted) and u201cindirect accessu201d meaning compatibility with a personu2019s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, Tim Hengeveld is the Design Lead,u00a0 JB Audras is the Docs Lead, and Monika Rao the Test Lead. nnnn

All release decisions will ultimately be this release teamsu2019 to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.nnnn

Release Schedulennnn
17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 and #4
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 and #6
6 January 2021Bug Scrub #7 and #8
12 January 2021Bug Scrub #9 and #10
21 January 2021Bug Scrub #11 and #12
27 January 2021Bug Scrub #13 and #14
01 February 2021Bug Scrub #15
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:rr ta description of the change;r tthe decision that led to this changer ta description of how developers are supposed to work with that change.rrDev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16
08 February 2021Bug Scrub #17
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18
16 February 2021BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3, continue writing Dev Notes and About page, soft string freeze
22 February 2021Bug Scrub #19
23 February 2021Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook. nnnn

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever ud83dude09nnnn

If you want to dive deeper into 5.7, join the weekly meetings in the #coreu00a0SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, which occur next atu00a0Wednesday at 05:00 UTC and Wednesday at 20:00 UTC. nnnn

Wish us luck!


Source