[jboss-dev] EJB3 Release Schedule

[Andrew Lee Rubinger]

Hehe, not true.  I'm now cursing it at a daily resolution. :)

The problem is that the build tool doesn't mesh with the JBoss Version 
Guidelines - using the form "1.0.0.GA" the DefaultArtifactVersion Unit 
Tests I have will fail getMajorVersion() and getQualifier().  This kills 
the ability to implement version ranges as a solution to obtain 
Continuous Integration.  Leading to problems like I posed the other day 
where jboss-metadata was stale and broke the build upon upgrade. :)

So what EJB3 is doing is succumbing to the version conventions that 
Maven is imposing.

2 things that would ease the pain:

* Pluggable version formats
* Pluggable dependency resolution

Until then we cobble together a working solution as we can.

S,
ALR

Dimitris Andreadis wrote:
> You are "implicitly" maven lovers, that's it.
> 
> Andrew Lee Rubinger wrote:
>> The "GA" is implicit.
>>
>> This way, we don't have redundant/confusing qualifiers.  Our next 
>> release will be 1.0.1.  Then 1.0.2.  Otherwise would we do:
>>
>> 1.0.0-SP1?
>> 1.0.1-GA?
>> 1.0.1-SP1?
>>
>> ..and after that:
>>
>> 1.0.0-SP2?
>> 1.0.2-SP2?
>>
>> So we'll continue along with the 1.0.x series, all GA, until our next 
>> Betas are 1.1.0-Beta1, etc.
>>
>> S,
>> ALR
>>
>> Anil Saldhana wrote:
>>> ALR, should it not be 1.0.0.GA?
>>>
>>> Andrew Lee Rubinger wrote:
>>>> Last week we did the following:
>>>>
>>>> * Released 1.0.0 of all EJB3 subcomponents
>>>> * Updated the dependency chain and released jboss-ejb3-as-int:1.0.0-CR2
>>>> * Promoted 1.0.0-CR2 to 1.0.0
>>>> * Updated AS trunk, Branch_5_x, Branch_5_0 with EJB3 1.0.0
>>>> * Released the EJB3 Plugin 1.0.0[1], to patch JBossAS 5.0.0.GA with 
>>>> libraries needed to bring EJB3 1.0.0 current.
>>>> * Announced to our community[2]
>>>>
>>>> Looking forward we'll be pledging releases on the 2nd and 4th 
>>>> Fridays of the month.  In practice we'll be starting the process on 
>>>> Thursdays to meet the deadline.
>>>>
>>>> For our first straight-to-community release, all went pretty 
>>>> smoothly. Still TODO in future releases:
>>>>
>>>> * Better integrate release process w/ JBossQA
>>>> * Document procedures for release (ie. JBossNews updates to Twitter, 
>>>> blogs, Release Notes, README, etc)
>>>> * Continue to chip away at "the continuous integration problem", in 
>>>> that dependency updates are all manual, there's no 
>>>> re-tagging/repackaging of CRs into GAs, and the testing process is 
>>>> much longer than we'd like.
>>>> * Get documentation/tutorials into the picture (Jaikiran's revamped 
>>>> and updated the suite)
>>>>
>>>> S,
>>>> ALR
>>>>
>>>> References:
>>>>
>>>> [1] 
>>>> http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=132063 
>>>>
>>>> [2] http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149232
>>>>
>>>> Andrew Lee Rubinger wrote:
>>>>> After the 1.0.0-GA Release of the EJB3 Projects, we will continue 
>>>>> to push releases both to the community and into AS active branches 
>>>>> at a resolution of twice a month[1].  The EJB3 Team has not yet 
>>>>> agreed upon a formal schedule (ie. every 1st and 3rd Monday will 
>>>>> lead to occasional gaps in cases where a month has 5 Mondays).  
>>>>> After we've set this, we'll reply back to this list with a 
>>>>> commitment upon which the community and dependent projects (ie. AS, 
>>>>> WebBeans) may rely.
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development

-- 
Andrew Lee Rubinger
Sr. Software Engineer
JBoss, a division of Red Hat, Inc.
http://exitcondition.alrubinger.com