On Mon, Jun 27, 2011 at 11:40 PM, Howard Lewis Ship <[email protected]> wrote:
> You might be down to comparing fix dates against release dates as you
> update your POM/build.gradle to point at the temporary Nexus
> repository containing the pre-release artifacts.
>
> In other words, we're raining the bar on people wanting to use
> pre-release artifacts (today's alphas and betas) to make things much
> simpler for the 99% that just want to upgrade from a final release to
> a final release.
>
> Further, in terms of finding bug fixes, the release notes will be
> simpler (if longer), so they won't have to search through lots of
> different listings of fixed bugs ("in alpha 1", "in beta 5"). They'll
> be a single long list of bugs fixed in 5.3 (i.e., all bugs fixed since
> the previous stable release, 5.2).
>
> Again, this is simpler in every way except for the few people who wish
> to try out pre-release builds.
Again I don't see it that way and I'm sure I'm missing something obvious.
I think not having the releases (be there alpha beta gamma or omega)
out in the wild but only in the "restrict" circle of the people
wanting to try it out is something that reduce it's visibility and the
opportunity for bugs to came out.
This will reflect on the quality of "released code" (mean there what
you want). This will increase the time between each releases.
If you clearly state on which is the target for a particular release
cycle then you could declare a release as final otherwise is difficult
to do it, isn't it? And even doing it is still difficult due the the
"last minute bug" coming out...
Doing a good release process is very difficult and cannot be
simplified by a name, the current scheme works pretty well even with
the current 5.3 trunk which has gone thought pretty deep inner
changes...
Just my 2 cents
--
Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
