[OPEN-ILS-DEV] Making 3.1 support extension plans concrete

[Bill Erickson]

Hi Galen,

For my part, I think 6 months is reasonable and the dates are sane.  To the
extent I assist with back-porting patches, etc. I'm happy to commit to
continued support for 3.1.

Thanks,

-b

On Mon, Oct 15, 2018 at 5:00 PM Galen Charlton <gmc at equinoxinitiative.org>
wrote:

> Hi,
>
> We've discussed [1][2] the notion of extending the community support
> period for Evergreen 3.1 as part of easing the transition away from
> the XUL staff cilent, but I cannot find anywhere that we set a date on
> that extension. I think we should do so so that we can update the EOL
> page [3].
>
> So, I've got two questions. First, are we (in particular, folks doing
> backports, documentation updates, and builds) ready to commit time to
> that? Second, what should the end date be for general support of 3.1?
> To make a concrete suggestion, I propose adding six months, meaning
> that general support would end on 2019-10-05 and security fixes would
> end on 2020-01-05.
>
> [1]
> http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-08-08-15.00.log.html#l-117
> [2]
> http://libmail.georgialibraries.org/pipermail/open-ils-dev/2018-August/010558.html
> [3]
> https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Implementation and Services Manager
> Equinox Open Library Initiative
> phone:  1-877-OPEN-ILS (673-6457)
> email:  gmc at equinoxInitiative.org
> web:  https://equinoxInitiative.org
> direct: +1 770-709-5581
> cell:   +1 404-984-4366
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20181015/aae4e997/attachment.html>