Next Thursday morning, we'll branch the 5.2.x release branch which will spawn 5.2.0.CR1 and 5.2.0 itself. All bugfixes and documentation updates should be pushed by Wednesday 27-APR evening to master. Don't push any risky new features to master at this time. Note that the documentation is included in the download zips, so changes to the documentation after the branch date won't make the download zip of 5.2.0.

Mark's just asked me to postpone the branching to tomorrow morning (Friday) instead of today (Thursday). Most (all?) are still working on fixes for CR1 or final, so that should be fine. Schedule: - Friday 7:00 GMT: branching 5.2.x from master => master will be 5.3.0-SNAPSHOT from then on - any commits for CR1 need to be manually cherry picked from master to the 5.2.x branch - Sunday 12:00 GMT: release CR1 from 5.2.x branch - any commits for final need to be manually cherry picked from master to the 5.2.x branch - Wednesday (maybe Thursday): release final from 5.2.x branch (more info later) Op 21-04-11 18:18, Geoffrey De Smet schreef: > For clarity: Any bug you want to fix for CR1 should go to the master branch. > Do no longer use the 5.2.0.M2.x branch. We're releasing M2 now and after > that it's dead. > > Op 21-04-11 17:43, Geoffrey De Smet schreef: >> Next Thursday morning, we'll branch the 5.2.x release branch which will >> spawn 5.2.0.CR1 and 5.2.0 itself. >> >> All bugfixes and documentation updates should be pushed by Wednesday >> 27-APR evening to master. >> Don't push any risky new features to master at this time. >> >> Note that the documentation is included in the download zips, >> so changes to the documentation after the branch date won't make the >> download zip of 5.2.0. >>