[jboss-dev] No more snapshots in 5.0!

[Jason T. Greene]

A couple of commonly used options:

Alpha3 - Who expects alphas to work anyway? :)
M12 - (Milestone 12)
N20090220-1200 - Nightly build 02/20/2009 at 12:00
I20090220-1200 - Integration build 02/20/2009 at 12:00


Ales Justin wrote:
> I'm fine with temp releases, as it's quite easy to do this once you have 
> your project fully mavenized.
> 
> But we need some common/general consensus on how this is gonna be done.
> Perhaps Alpha, Beta are not the way to go, as we already treat them as 
> "official" releases.
> 
> What is 'normally' used in this case?
> 
> Jason T. Greene wrote:
>> We need to stop using snapshots in this Branch, as it's making it 
>> difficult for everyone to figure out why their tests are suddenly 
>> breaking. As an example, Brian is now trying to find the cause of a 
>> deadlock issue that just appeared on a testrun without any changes 
>> occuring.
>>
>> We need to use releases so that a test run can be correlated to a 
>> component change. Even if you don't call it an official release, just 
>> make up something like M132 or Beta17, etc.
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development


-- 
Jason T. Greene
JBoss, a division of Red Hat