> -----Urspr�ngliche Nachricht-----
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] Im
> Auftrag von Howard M. Lewis Ship
> Gesendet: Dienstag, 25. Juni 2002 16:20
> An: Richard Lewis-Shell
> Cc: Tapestry Developer
> Betreff: Re: [Tapestry-developer] binding problem
> 2.0.5 (rc for 2.1)
> 2.1 (note: no '.0')
> 2.2-alpha-1 (incremental releases, equivalent to dot releases)
> 2.2-alpha-2
> 2.2-beta-1 (first release candidate)
> 2.2-beta-2 (second release candidate)
> 2.2
>
> This would more clearly identify the stability of the
> release, and would more clearly show how the alpha's and
> beta's are leading up to the next minor release. Perhaps, in
> the future, the alpha and beta release would occur in a
> development branch (there would be a 2.2-dev, or even a
> 2.2-hship-dev branch).
> > As always - this is meant constructively. You're doing a
> great job...
That sounds good, but maybe its better to keep the "newest and greatest"
in HEAD, and create a 2.1 branch when 2.1 is released, and maybe later
release a bugfix release 2.1.1 out of the 2.1 branch.
Regards
chris
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
