If you're going to have regular, consistent, and fairly frequent
releases, then I'd leave 5.0.1, 5.0.2, etc. as patch updates for bug
fixes only. But if you want newer functionality not in 5.0.x that's
slated for 5.1, then track 5.1-SNAPSHOT - but don't expect it to show
up in 5.0.25.
Is that a fair assessment Howard?
Christian
On 15-Jul-08, at 12:06 , Hilco Wijbenga wrote:
On Mon, Jul 14, 2008 at 11:20 PM, Howard Lewis Ship
<[EMAIL PROTECTED]> wrote:
I'd rather we have a process where we can come out with a 5.1, 5.2,
5.3 release every few months. That's my vision, anyway, add a couple
of significant features, work towards a GA release, lather rinse
repeat.
Wouldn't that then also allow subprojects to release in between using
5.1.x, 5.2.y, etcetera? I mean, can't we have both? It doesn't seem
too difficult to come up with some sort of scheme that allows
subprojects to release bug fixes right away without losing the ability
to easily identify what Tapestry release the subproject belongs to.
(The next Tapestry release could then bump everything up to 5.z so
that all versions are the same again.)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
