]
Max Rydahl Andersen commented on JBIDE-4200:
--------------------------------------------
"If the N build contains newer bits (was built later) then it should replace the R
regardless of quality statement (phase/type). You don't want older bits to take
priority over newer ones;"
I disagree. The timestamp is only *secondary*.
2.0.0.R<timestamp> should overrule any 2.0.0.N<timestamp> builds.
2.0.1.N<timestamp> should overrule any 2.0.0.(R|N)<timestamp> builds.
"that would prevent a user from upgrading from 2.0.0R -> 2.0.1N and then later to
2.0.1S before picking up the final 2.0.1R. We want a seamless chronological flow for early
adopters, right?"
Why is 2.0.0.R -> 2.0.1.N prevented ? I don't understand - the .z version his
updated.
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: