If Keith has an itch in 4.1 branch - and if he can find 2 more +1 votes, than it's his right to have a release, and the 4.1 branch will become "maintained". A branch is maintained if there are committers interested to maintain it - not if someone else decides it shouldn't be maintained and they should do something else.
4.1 is stable and works good enough - yes, 5.x is faster and has better architecture, but some people don't like to change production systems very often, and it is very good for them to know that what they are using is still maintained ( we're not msft to make money by forcing people to upgrade )
Costin
Shapira, Yoav wrote:
Hi,
<ballot> The 4.1.31 maintenance release should happen: [ ] Yes [ X ] No </ballot>
-1 on this release. Reasons have been stated in detail in the other thread, but to summarize this branch is no longer maintained and users should upgrade to 5.x or custom-patch if they have an emergency.
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
