Going forward we need to enforce use of the PDE API tooling so people
are compelled to update their plugins' manifests correctly, and only
need update feature versions when the actual feature content changes
(not the included plugins). Using feature version hash suffixes and
qualifiers which always increment chronologically (x.y.z.vYYYYMMDDhhmm
rather than x.y.z.CR2) will also ensure that new code can always be
installed on top of old code, even if someone forgets to bump a number.
Or, we do what Prakash wanted and just bump everything up from x.0.0 to
(x+1).0.0 with every release. Big numbers are easier to sell, right? :)
I'll updated as & archives to their x.0.1.GA versions.
Should Hibernate be at 3.2.5, or have other service releases happened in
between? Currently we have this:
# The release prefix for this release
hibernate.tools.release=3.2.4
N
Max Rydahl Andersen wrote:
Hibernate needs updating too afaik, but for some weird reason we are
versioned as GA in this file (which is correct) but should get updated a
number in its other file.
as and archives also received fixes afaik.
Same with ws.
Actually, I think svn diff between 3.0.0.GA and 3.0.1.GA will be the
safest/fastest way of checking this....otherwise i'm sure we will miss
some.
/max
Nick Boldt wrote:
> I need to know which components have incremented their overall feature
> version. Here's what we had for {2,3}.0.0.GA:
>
> # component versions, JBT
> richfaces=3.0.0.GA
> archives=3.0.0.GA
> as=2.0.0.GA
> freemarker=1.0.2.GA
> jbpm=3.1.7.GA
> hibernate-tools=GA
> seam=3.0.0.GA
> struts=3.0.0.GA
> esb=1.1.0.GA
> tests=3.0.0.GA
> ws=1.0.0.GA
> birt=1.0.0.GA
> portlet=1.0.0.GA
> tptp=1.0.0.GA
> smooks=1.0.0.GA
> drools-ide=5.0.0.CR1
> examples=1.0.0.GA
> jbpm-convert=1.0.0.GA
> jmx=1.0.0.GA
> xulrunner=1.0.0.GA
>
> # component versions, JBDS
> equinox-transforms=1.0.0.GA
> runtime=1.0.0.GA
>
> If your component is now on x.y.1, let me know. I can dredge thru SVN
> for this information, but it's hella faster if you can just tell me. :)
>
> Thx,
>
> Nick
>
> Nick Boldt wrote:
>> 3.0.1.GA / 2.0.1.GA have been tagged in SVN, and the first builds
>> will start soon:
>>
>>
http://hudson.qa.jboss.com/hudson/job/jbosstools-release-3.0.x/
>>
http://hudson.qa.jboss.com/hudson/job/devstudio-release-2.0.x/
>>
>> Meanwhile, QA keeners can start on these N builds:
>>
>>
http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.0.x/ (#52)
>>
http://download.jboss.org/jbosstools/builds/nightly/3.0.1.Alpha1/20090428...
>>
>>
http://download.jboss.org/jbosstools/updates/nightly/3.0.x/
>>
>>
http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-2.0.x/ (#64)
>>
http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.0.1.Alpha1/200904...
>>
>>
http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/2.0.x/
>>
>> Nick
>>
>> Max Rydahl Andersen wrote:
>>> Hi,
>>>
>>> As discussed last week the 3.0.1 branch now has a code freeze and
>>> you should not be committing to this branch without approval from
>>> either me or Denis.
>>>
>>> Nick will follow up to this email with links to the builds QA and
>>> those have fixed issues should be using when testing the release.
>>>
>>> Thanks,
>>> /max
--
Nick Boldt :: JBoss, a division of Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Eclipse Modeling & Dash Athena
http://wiki.eclipse.org/User:Nickb