missed the board list
-------- Original Message --------
Subject: Re: First community release
Date: Tue, 29 Nov 2011 13:32:27 -0500
From: Jon Choate <jchoate(a)redhat.com>
On 11/29/2011 12:58 PM, Barak Azulay wrote:
On 11/29/2011 05:59 PM, Livnat Peer wrote:
> On 11/07/2011 06:51 PM, Carl Trieloff wrote:
>> At the workshop in the release / roadmap working session we agreed that
>> around November 16th we see how all the distro's are making out in
>> creating a release for oVirt and set the date for the first community
>> Please have your comments / feedback for that time period, at which
>> point I will start the release discussions.
>> Board mailing list
> Hi All,
> Not sure where we stand with the first release but I think we should
> take into account the jboss version we use before releasing.
> We currently deploy on jboss as 5, but we started working on deployment
> on jboss as 7.
> Releasing on AS 5 and then moving to AS 7 might require some upgrade
> path and it is a time consuming task to do that.
> Since we already started working on the deployment on jboss AS 7, I
> think it might worth holding back first 'formal' release until it is
> done. It will help us avoiding upgrade support and get all the benefits
> of using as7 (startup time, memory/cpu foot-print etc.) - get better
I think we should aim for a fast first release, meaning ASAP on jboss 5
The questions are:
1 - what is a release? a tag in all the repos to be picked up by each
2 - do we have any criteria on what is good enough for a release ? or
any point in time that everybody feels ready?
I like to approach the idea in reverse:
1 - What is preventing us from releasing today?
2- Are these really worth holding up the release?
3 - What can we do today so that the issues in #1 are gone tomorrow?
I too am unsure what a release really means when people can get the code
any time that they want and we could declare a release whenever and as
often as we want.
> Board mailing list
Arch mailing list
Arch mailing list