[JBoss JIRA] Created: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
12:21 a.m.
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
Priority: Minor
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
12:27 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-4200:
------------------------------
Attachment: devstudio-trunk.patch
Patch to change suffixes on jars/zips.
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
Priority: Minor
Attachments: devstudio-trunk.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
12:27 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-4200:
------------------------------
Attachment: mylyn-context.zip
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
Priority: Minor
Attachments: devstudio-trunk.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
12:50 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt reassigned JBIDE-4200:
---------------------------------
Assignee: Nick Boldt
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: Minor
Attachments: devstudio-trunk.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
3:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4200:
--------------------------------------------
hmm - I can't download the patch ... could you reattach it ?
What is phase set to for releases ?
With respect to this change does eclipse got a writeup why it is better to have the date
being the siginificant qualifier ?
My problem with this is that a nightly build:
3.1.0.v200911091234-M1-H5-N
would be considered "updatable" from this release build:
3.1.0.v200910091234-R1-H5-R
Where as in the "old" system we had the release qualifer earlier in the name
meaning no nightly builds of 3.1.0 could ever overwrite a Release build (which imo is how
it should be since any nightly build with a newer date but same "old" version is
a bad thing)
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: Minor
Attachments: devstudio-trunk.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
11:13 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-4200:
-----------------------------------
We will never have two builds of different types w/ the same timestamp.
And when we switch to use different tags in the maps, so that individual plugins/features
only change when their contents change (rather than with every build, as we do it now),
then it won't matter if a jar is built via an R or N build, because the bits will be
identical, right down to the generated feature suffix hash/digest.
We can also make the naming a little smarter:
3.1.0.v200911091234-M1-H5-N
3.1.0.v200911101234-M1-H9-R
...
3.1.0.v200911091234-RC1-H20-N
3.1.0.v200911101234-RC1-H25-R
...
3.1.0.v200912091234-R-H30
I suppose really the type suffix is meaningless at this point since an N build == an R
build except for that letter. We could drop the buildType suffix entirely.
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: Minor
Attachments: devstudio-trunk.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
1:40 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4200:
---------------------------------
Fix Version/s: 3.1.0.M1
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: Minor
Fix For: 3.1.0.M1
Attachments: devstudio-trunk.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
7:14 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4200:
--------------------------------------------
We will never have two builds of different types w/ the same
timestamp.
No, but you could have a nightly of 3.1.0 that is built after the R build meaning it will
override it which is why I don't understand why the type is not first and timestamp
*later* ?
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: Minor
Fix For: 3.1.0.M1
Attachments: devstudio-trunk.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
7:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4200:
--------------------------------------------
sorry, type should probably be phase in that sentence, i.e. M1, RC1 and R should be after
the v and before the timestamp.
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: Minor
Fix For: 3.1.0.M1
Attachments: devstudio-trunk.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
9:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt 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; 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?
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: Minor
Fix For: 3.1.0.M1
Attachments: devstudio-trunk.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
11:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-4200:
-----------------------------------
http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/trunk/ shows label is Dev,
not Nightly, though the build type is N.
http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/2.0.x/ shows label is
Nightly for type N.
Must have missed something between branches.
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: Minor
Fix For: 3.1.0.M1
Attachments: devstudio-trunk.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
1:30 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4200:
---------------------------------------
Fix Version/s: 3.1.0.M3
(was: 3.1.0.M2)
slip - but we need to put this to rest soon ;)
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: Minor
Fix For: 3.1.0.M3
Attachments: devstudio-trunk.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
5:07 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4200:
---------------------------------------
Priority: Blocker (was: Minor)
put as blocker for M4 - either it gets fixed there or we close it.
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: 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.M3
Attachments: devstudio-trunk.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
5:36 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4200:
---------------------------------------
Fix Version/s: 3.1.0.M4
(was: 3.1.0.M3)
slip to next version.
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, 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
9:37 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-4200:
------------------------------
Attachment: JBIDE4200x3.patch
patch for three branches: trunk, 2.1.x, 3.0.0.M3
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.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
9:50 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-4200:
------------------------------
Attachment: JBIDE4200x3-part2.patch
addendum
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
8:30 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
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
4:41 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt resolved JBIDE-4200.
-------------------------------
Fix Version/s: 3.1.0.M3
(was: 3.1.0.M4)
Resolution: Done
Fixed for 3.0.2.GA / 2.1.0.GA, 3.1.0.M3 / 3.0.0.M3 + beyond.
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.M3
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
6068
days inactive
6212
days old
jbosstools-issues@lists.jboss.org
18 comments
3 participants
participants (3)
-
Denis Golovin (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)