on 11/27/2000 4:23 PM, "Gunnar R|nning" <[EMAIL PROTECTED]> wrote:
> The theory behind release early, release often is that you at every point
> during your development lifecycle has something to showoff. By doing this
> you reduce risk, improve quality, improve progress visibility etc.
>
> Isn't most apache projects encouraged to have working CVS versions at all
> times ? This implies that Apache projects indeed practice release early and
> often - which in turn leads to higher quality of the code that is _labeled_
> as released.
Right, but if you look at the httpd project, lets see, version 2.0 has been
about 3 years in the making and releases are made only after much careful
testing. In fact, before a release is made live, it is tested on the
new-httpd list first. That is why some version numbers have been skipped in
the past.
None of these practices have happened under the Jetspeed project.
If you want release often, then download a daily snapshot. Those are labeled
with the date that they were built.
Again, the ASF is simply about quality releases that you can count on as
production quality software. I personally think that more OSS projects
should work like that as the people who are going to be contributing to your
software are generally the same people who can figure out how to get it from
CVS.
-jon
--
twice of not very much is still a lot more than not very much
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
