REMINDER: IMPORTANT: Rampdown / stabilization of 8u20 for milestone M2
As a reminder: We are approaching the M2 freeze as described in #5 below. All approved (see #4) changesets for the M2 milestone build should be pushed by 11:00 PM Pacific time on Sunday, Feb 23. -- Kevin Kevin Rushforth wrote: Hi OpenJFX committers, After this coming Monday's FX build, which will go into 8u20-b02, we will start ramping down for our M2 milestone build (aka 8u20-b03). This particular milestone is important for the embedded platform. As a result, you will need to observe the following rules for any commit. 1) Sunday, Feb 16 at 11:00 pm Pacific time: All planned changes for b02 should be in (our test build is scheduled to start at 11pm that day). The usual rules apply for changesets pushed prior to that time. 2) All changesets that are pushed after 11:00 pm Pacific time on Sunday, Feb 16 will need additional scrutiny to go in. In addition to your normal reviewer you must get a +1 from one of the following, even if you would normally do a post-commit review: Daniel Blaukopf Steve Northover Kevin Rushforth Lisa Selle 3) Monday, Feb 17: We will do our usual (In)Sanity Testing and then hand off the bits to release engineering for 8u20-b02. 4) Week of Feb 17 - 14: Bug fixes can go in subject to the extra approval noted above, but please hold off making any risky changes until after M2. 5) Sunday, Feb 23 at 11:00 pm Pacific time: We will do a soft freeze, during which time we will be locked except for critical issues discovered during testing, for b03 (milestone M2). 6) Monday, Feb 24: We will do our usual (In)Sanity Testing, with extra emphasis on testing anything that changed after b02, and then hand off the bits to release engineering for 8u20-b03. 7) I will send a subsequent announcement as to when the repo is open for normal business. Thank you. -- Kevin
Re: IMPORTANT: Rampdown / stabilization of 8u20 for milestone M2
Note that changes to IDE files, JavaDoc and other things that do not affect the M2 bits can be released as usual. Having said that, the day before the final freeze would not be a good one to release a billion JavaDoc changes and blow the mind of the release engineers! Steve On 2014-02-14 9:17 AM, Kevin Rushforth wrote: Hi OpenJFX committers, After this coming Monday's FX build, which will go into 8u20-b02, we will start ramping down for our M2 milestone build (aka 8u20-b03). This particular milestone is important for the embedded platform. As a result, you will need to observe the following rules for any commit. 1) Sunday, Feb 16 at 11:00 pm Pacific time: All planned changes for b02 should be in (our test build is scheduled to start at 11pm that day). The usual rules apply for changesets pushed prior to that time. 2) All changesets that are pushed after 11:00 pm Pacific time on Sunday, Feb 16 will need additional scrutiny to go in. In addition to your normal reviewer you must get a +1 from one of the following, even if you would normally do a post-commit review: Daniel Blaukopf Steve Northover Kevin Rushforth Lisa Selle 3) Monday, Feb 17: We will do our usual (In)Sanity Testing and then hand off the bits to release engineering for 8u20-b02. 4) Week of Feb 17 - 14: Bug fixes can go in subject to the extra approval noted above, but please hold off making any risky changes until after M2. 5) Sunday, Feb 23 at 11:00 pm Pacific time: We will do a soft freeze, during which time we will be locked except for critical issues discovered during testing, for b03 (milestone M2). 6) Monday, Feb 24: We will do our usual (In)Sanity Testing, with extra emphasis on testing anything that changed after b02, and then hand off the bits to release engineering for 8u20-b03. 7) I will send a subsequent announcement as to when the repo is open for normal business. Thank you. -- Kevin
IMPORTANT: Rampdown / stabilization of 8u20 for milestone M2
Hi OpenJFX committers, After this coming Monday's FX build, which will go into 8u20-b02, we will start ramping down for our M2 milestone build (aka 8u20-b03). This particular milestone is important for the embedded platform. As a result, you will need to observe the following rules for any commit. 1) Sunday, Feb 16 at 11:00 pm Pacific time: All planned changes for b02 should be in (our test build is scheduled to start at 11pm that day). The usual rules apply for changesets pushed prior to that time. 2) All changesets that are pushed after 11:00 pm Pacific time on Sunday, Feb 16 will need additional scrutiny to go in. In addition to your normal reviewer you must get a +1 from one of the following, even if you would normally do a post-commit review: Daniel Blaukopf Steve Northover Kevin Rushforth Lisa Selle 3) Monday, Feb 17: We will do our usual (In)Sanity Testing and then hand off the bits to release engineering for 8u20-b02. 4) Week of Feb 17 - 14: Bug fixes can go in subject to the extra approval noted above, but please hold off making any risky changes until after M2. 5) Sunday, Feb 23 at 11:00 pm Pacific time: We will do a soft freeze, during which time we will be locked except for critical issues discovered during testing, for b03 (milestone M2). 6) Monday, Feb 24: We will do our usual (In)Sanity Testing, with extra emphasis on testing anything that changed after b02, and then hand off the bits to release engineering for 8u20-b03. 7) I will send a subsequent announcement as to when the repo is open for normal business. Thank you. -- Kevin
