Hello,

until now we have asked developers to hold off their patches during the final 
week of the release cycle, while QA tests the various canary releases to 
determine the best branch point. This was pointed out to be ineffective and 
against the idea of "developers keep working on master undisturbed" that the 
release process is supposed to facilitate.

Therefore we are doing the following changes starting with Crosswalk 7:


*         No more "code freeze" in Canary

*         The branch always happens at the fixed date indicated in 
https://crosswalk-project.org/#wiki/Release-dates

*         By the end of 4th week of the release cycle we finalize what features 
are in scope of the next Beta and need to be verified by QA

Note that we will not rush in PRs at the last minute (i.e. last week) before 
the branch with the rationale that they must be part of the release. If they 
had to, they should have been submitted earlier. We will however ask owners to 
prioritize reviews related to features in scope of the release.

Regards,

Francesco
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to