-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hmmm...
What is your projected timeframe for a 4.1 release?
Reason I ask: If it's going to be a while, would your sentiment still
hold true if I were to take on the responsibility of merging the 4.0.X
changes into your 4.1? Especially for 4.0.3 (what has been resolved and
is currently in JIRA slated for 4.0.3), most of the changes are
documentation - but some of that documentation is in Javadoc. There are
still more changes that Andy and I have marked for 3.0.5 and 4.0.3 -
some of which add (small?) features (which prompted my question about
whether it should be 4.1 instead of 4.0.3) but is still backward compatible.
If it's decided to go with the X.Y.Z method of release numbering (which
I believe is pretty standard across the board), would it change anything
to move your work to 4.2 and release 4.1 with what's currently marked
4.0.3? Again, I'd be willing to merge up with you instead of you merging
back from us.
("compelling" is always very subjective. :-))
Brian
Jesse Kuhnert wrote:
> If at all possible I'd like to avoid a 4.0.3 release, unless there is a
> very
> compelling reason to make one.
>
> There are still a few svn merges that need to happen from the 4.0.X to
> 4.1branches but I ~hope~ everything remains backwards compatible as
> is.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEVnEMaCoPKRow/gARAo2LAKDK3sxnEPha/Qpt+Ago/tBdDf4knACdGXgg
aZuBP+dGp3Yaj2PEKe+fVEc=
=wcU3
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
