> We will have a 2-day test pass against M7 on 15th and 16th. 

This is wrong, as you can see from 
https://www.eclipse.org/eclipse/development/plans/freeze_plan_4_7.php.

We will have the usual test pass on Monday and then also use Thursday and 
Friday in the milestone week to test.

Dani



From:   "Sravan K Lakkimsetti" <[email protected]>
To:     [email protected], Equinox 
<[email protected]>, [email protected], "Eclipse Platform UI 
component developers list." <[email protected]>
Date:   05.05.2017 12:32
Subject:        [platform-releng-dev] Eclipse Oxygen(4.7) M7 Reminders
Sent by:        [email protected]



Hi,

Eclipse Oxygen M7 Stabilization starts next week with a goal to deliver on 
May 12, 2017. 

The build schedule has been updated and can be downloaded from here.

Important Note: We have feature freeze this milestone and start RC 
phase/end game from subsequent weeks. Please read end game plan here 
http://www.eclipse.org/eclipse/development/plans/freeze_plan_4_7.php. We 
will have a 2-day test pass against M7 on 15th and 16th. Also all the RCs 
are 1 week each this time. There won't be much time 

Please refer to 
https://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg10375.html for the 
end-game plan announcement

Please note 
Monday: Last day of development (and even then, no "big changes"). After 
Monday 20:00 ET, no feature work or unrelated fixes are allowed -- only 
regression fixes. 
Tuesday: All-day test pass. Nobody should develop or fix anything. 
Literally spend the entire day testing. 
Wednesday: Fix day with a focus on fixing regressions found during the 
test day (Tuesday). No unrelated fixes. Review and thoroughly test all 
commits. 
The last Wednesday build is the release candidate every team signs off on 
Thursday. 
The "New and Noteworthy" entries are due on Wednesday evening:
Git repo: ssh://git.eclipse.org/gitroot/www.eclipse.org/eclipse/news.git
Gerrit: ssh://git.eclipse.org:29418/www.eclipse.org/eclipse/news.git
Live website: https://www.eclipse.org/eclipse/news/4.7/M7/ 
Thursday: Sign-off after re-testing, or at least confirming no changes 
have been made to your component's code since the last time the component 
was tested well. 
Friday: Build is officially declared and made available. 
The master branch stays closed until the milestone is officially released. 
(That is, it is not enough that your component has signed off.)

No new code changes can be made until the milestone is officially 
declared. That is, it is not enough that your component has signed off.


Thanks and Regards,
Sravan 

Sravan Kumar Lakkimsetti
IBM India Pvt Ltd,
Embassy Golf Links Business Park, D Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India
Phone: 91-80-41776858_______________________________________________
platform-releng-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________
equinox-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to