[jbosstools-dev] Re: ACTION REQUIRED: Has your component's feature version incremented in 3.0.1 branch? (was Re: Code freeze of 3.0.1 branch)

[Denny Xu]

WS and ESB components were changed and need to update its feature 
version numbers,  but I not sure what version number I should update 
them to,
just update to 3.0.1, right? is there a version number increment rule?

Denny


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/200904280907/ 
>>
>> 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/200904280358/ 
>>
>> 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
>>>
>>
>