[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-4200:
-----------------------------------
It's the "and then later" part that would fail. Qualifiers must increase
lexicographically, and in the ASCII table, S >> N, even if the N is newer. So we
need to ensure that newer bits are always labelled newer than older bits, and that the
build type is simply a descriptor, not a determinant.
So, currently, I'm going with this:
3.1.0.v200909101234N-H123-M3
because it includes everything you need to know (major.minor.service, timestamp, type,
buildID, and phase/vanity name.
Change qualifiers on zips and jars to support Milestones and RCs
instead of Alphas, Betas, CRs, GA
--------------------------------------------------------------------------------------------------
Key: JBIDE-4200
URL:
https://jira.jboss.org/jira/browse/JBIDE-4200
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 3.1.0.M4
Attachments: devstudio-trunk.patch, JBIDE4200x3-part2.patch, JBIDE4200x3.patch,
mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Jars and zips currently look like 3.1.0.Alpha1-yyyymmddHHMM-H###
To support a more Eclipse-like naming convention involving milestones, we need to switch
to:
3.1.0.vyyyymmddHHMM-PP-H###-T
Where PP = phase, eg., M1, H### = Hudson build number, and T = type, eg., N, I, S, or R.
(Only N and R are currently supported.)
This will guarantee that regardless of where a build is produced (ie., in whatever phase)
it can always be installed onto an older version because the qualifier will always
increase w/ time, regardless of additional suffixes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira