Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-releng-dev] tagging and branching for 3.5


Several people have asked me about tagging for the 3.5 release

Just to recap, I don't tag the org.eclipse.releng project until we have shipped 3.5.  Then I'll branch the org.eclipse.releng project for the 3.5.1 maintenance stream.  I don't branch all the projects for the maintenance stream.  Teams are responsible for branching their projects as required for 3.5.1 builds. 3.6 development will start in HEAD.

Some components have started releasing fixes to HEAD which is fine.   However, please be cognizant that if you have to release a fix for a 3.5 critical stop ship bug, you'll need to branch the last 3.5 version of this project  if it has been updated.

Also, please don't update the tags of the projects in the HEAD version of releng project until we have shipped 3.5.

thank you,

Kim

Back to the top