No subject

I've said this before on this list, but whatever the release cycle needs to be in order to keep a good development pace (because keeping developers going strong is obviously a huge priority for open source projects), I would be most comfortable with a timed support policy (probably 12 months minimum) so we can plan our upgrade windows far into the future and not just around whenever the development team deems that a new release is appropriate.

That's my two cents! ;-)

Thanks for bringing this issue to the list, Jason.

Chris

----- Original Message -----
> From: "Jason Etheridge" <jason at esilibrary.com>
> To: "Evergreen Discussion Group" <open-ils-general at list.georgialibraries.org>, "Evergreen Development Discussion List"
> <open-ils-dev at list.georgialibraries.org>
> Sent: Friday, September 23, 2011 3:32:48 PM
> Subject: [OPEN-ILS-GENERAL] community support policy for Evergreen releases?
> During the Community meeting in IRC today, I asked "if we really want
> to push out 2.2 quickly, might we extend support for whatever version
> would be falling off the support truck? or is that a bad idea?"
> 
> According to the last policy we came up with, 1.6 would be deprecated
> as soon as 2.1 hits, and 2.0 will be deprecated as soon as 2.2 hits.
> There were musings about time-based support periods and Long Term
> Support releases, and it was decided we'd talk about such things on
> list.
> 
> So. Discuss. :)
> 
> --
> Jason Etheridge
> | Equinox Software, Inc. / Your Library's Guide to Open Source
> | phone: 1-877-OPEN-ILS (673-6457)
> | email: jason at esilibrary.com
> | web: http://www.esilibrary.com

-- 
Chris Sharp
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, Georgia 30345
(404) 235-7147
csharp at georgialibraries.org
http://pines.georgialibraries.org/