I agree, a lifecycle for maintenance should be set and standardized for each installation. Are you versioning on an standard or just whenever enough bugs become evident to warrant?
Jon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Wednesday, March 28, 2007 8:27 PM To: [email protected] Subject: Re: [wp-testers] Re: 2.0.10 and 2.1.3 Release Candidates Yes, otherwise, well, you might have to give up sleeping. :P No, I don't think you should maintain every release, every 3 or 4 release being maintained sounds good. But, they should only be maintained for like 6 months or something, just to give people time to upgrade, no to give people a reason not to update. :P On 3/28/07, Ryan Boren <[EMAIL PROTECTED]> wrote: > > On 3/28/07, Matt <[EMAIL PROTECTED]> wrote: > > Sweet... When 2.2 is released, is 2.1 going to be maintained for awhile > like > > 2.0 is? > > Since we're doing a much faster release cycle, we're not going to > maintain 2.1. We'll do 2.2.x as needed until 2.3 comes out. For 2.3 > or 2.4 we'll make an extended maintenance commitment. I don't think > we can do maintenance for every 2.x release and remain sane. Maybe > maintaining every third release would be reasonable. > > Ryan > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > -- Matt ([EMAIL PROTECTED]) http://mattsblog.ca/ _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
