portals-pluto-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David H. DeWolf" <ddew...@apache.org>
Subject RE: Defining the release
Date Tue, 21 Sep 2004 13:28:24 GMT
Would you give us an overview of our options for the upcoming release?
There are several different approaches that Apache projects take.  Some,
like struts, create builds and then vote on their quality (Alpha, Beta, GA).
Other seem to define releases as "release candidates", have different naming
conventions and different processes.  Do we have a plan yet for our release

Also, the word "release" can be confusing simply because often people assume
that means general availability.  IMHO we're not at the level yet and we
should definitely cut several 'release candidates', before publishing a full
general availability release.  In my mind, this upcoming "release" should be
put out as an alpha release, or snapshot, or whatever we want to call it. 

The benefit of an alpha release is that people are able download an actual
release (as opposed to downloading through cvs).  This stabilizes their
experience and makes it a little easier to get involved.  The hope would be
that having a release of this type out would prompt more users to join the
community by using the application and providing feedback.


> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@apache.org] 
> Sent: Tuesday, September 21, 2004 2:53 AM
> To: pluto-dev@portals.apache.org
> Subject: Defining the release
> We planned to do our first public release by the end of 
> september which is
> next week. We have 15 open issues in Jira.
> The question is now, which of them need *really* to be fixed for the
> release.
> Not everything has to be done in this release. It's better to 
> release early
> and release often than to try to do the "perfect release" 
> (which usually
> results
> in never releasing anything) :)
> Carsten 
> Carsten Ziegeler 
> Open Source Group, S&N AG
> http://www.s-und-n.de
> http://www.osoco.net/weblogs/rael/

View raw message