[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] questions about signoffs
|
Igor:
Here's some brief information [1], but I'll explain in more detail.
[1]
http://wiki.eclipse.org/Ganymede/Signoffs#LegendTraditionally, the Eclipse Platform (and several other projects) have promoted I or S builds and then later simply renamed them to their final state. For example, an RC build may be renamed to R if nothing needs to change between the release of the RC and the date the R is due. The same is true for I builds being renamed to their Stable/Milestone names.
Some projects simply spin an S or R build when it's time for a milestone/release candidate/release build instead of bothering with the rename. If your consumers aren't concerned about binary compatibility between "last week's RC" and "this week's R", and you don't mind respinning to build the newer build, then the P state can simply be skipped entirely.
Or, if you have technical reasons for not wanting to use the "x.y.zMn" and "x.y.zRC*" milestone/RC naming conventions, you can skip the R state and just use the P state.
The distinction is only really meaningful if you have downstream consumers waiting to know that you're done so they can adopt your bits, or update their build info to point to your renamed build.
In the past, emails have been sent saying "build I20070612-1234 is our release candidate, and will be renamed to 3.3.0-R200706121234" when we release after the server freeze." Instead of that, this information can instead be conveyed in the RC and R columns.
As to how to rename, I have a script you can use if you would like, which I'll link in the wiki here [2].
[2]
http://wiki.eclipse.org/Ganymede/Signoffs#Renaming_Builds
