I have a bug fix to commit to the 2.1 branch but cannot do so until this
gets ironed out. At the moment we have deprecated code on the 2.1
branch. Since it is not appropriate to deprecate code during a bug fix
2.1.1 release, we are now unable to do such a minor release.
Options:
1. Do not issue any bug fixes releases for 2.1.x
2. Revert the deprecation changes on the 2.1 branch and have a 2.2
branch where deprecation can occur.
3. Branch the 2.1 branch to a 2.1.x branch just prior to the
deprecation changes and continue 2.2 development on the 2.1 branch (ugly
but easier than 2)
Our policy is to deprecate over a release such as 2.2-2.3 or 2.2-3.0,
but this serves little purpose if 2.2 is only going to be in place to
deprecate things. No one is going to upgrade for that reason. So maybe
(1) is the right choice and people have to upgrade to 2.2 to get any bug
fixes. But I do not like that. Is there any features that can be
slated for 2.2 now that 3.0 is in full gear?
Other opinions/options?
john mcnally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
