Hi All, Since we are now applying a more rigid schedule to major releases for Evergreen, perhaps we should do the same for maintenance releases. We've already agreed to generally do monthly maintenance releases. How about we elect a day each month for the release cutting? It can be flexible as needed, of course, but I think it's nice to have a default target.
There will be exceptions, like critical (data-eating) bugs / critical security fixes, but we can manage those on an as-needed basis. Since I'm bringing it up, I'll go ahead and suggest the 3rd Wednesday of each month. I like Wednesdays since they give us lead/recovery time in the form of business days. Plus the 3rd Wednesday of each month gives us some, but not too much, flub room to get the release out within the monthly window. For January, this would mean 2.3.3 and 2.2.5 would be released January 16th. -b -- Bill Erickson | Senior Software Developer | phone: 877-OPEN-ILS (673-6457) | email: [email protected] | web: http://esilibrary.com | Equinox Software, Inc. / Your Library's Guide to Open Source
