Freddy,
I hear you but I have a hard time depending on code in a trunk unless
there is a critical issue that I can't live without and need a fix for... .
Case in point today the trunk is fine and quite "usable" as you put it
but tomorrow after some "next commit" it might not be the case... or by
the time someone reads this thread on the mailing list archives it might
not be the case anymore. In the end, it is really up to the release
manager / development team to determine when in time the trunk of a
release is "stable" and "usable".
Of course it is also important that people test against upcoming
releases as much as possible. I am all for that and would love to test
1.6 assuming that by the time we are ready to release it is likely that
it is has gone GA (hence my request for a road map if there was one).
So what is the solution IMHO: what would get me and others working with
a release and feeling more "comfortable" is releasing some sort of
periodic "stable" and "usable" snapshot e.g. 1.6.0_snapshotX. Yes, I
know release management has its overhead that some will argue against
but the benefit of "release often" and "providing a road map" is greater
IMHO.
Regards,
--Nikolaos
Freddy Daoud wrote:
Hi all,
As for 1.6, well, I won't even guess. Sorry.
For what it's worth, I've been using the trunk of 1.6 for
quite a while now (because I love using the ObjectFactory)
and haven't had any problems.
I understand being reluctant to working with "unreleased"
code, but the current snapshot of 1.6 is quite usable.
Cheers,
Freddy
------------------------------------------------------------------------------
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
------------------------------------------------------------------------------
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
