[OPEN-ILS-DEV] Supported releases

Daniel Wells dbwells at gmail.com
Wed Jul 22 15:41:53 EDT 2020


Our initial agreement was to keep 3.1 in at least a security-only support
mode until every "webstaffblocker" had been dealt with.  I think we should
keep to our word on that.

There is just one open bug with that tag:
https://bugs.launchpad.net/evergreen/+bug/1773191

The bug has some movement, so maybe it can be closed out without much more
work.  Short of that, though, I would actually advocate we just remove the
tag from that bug.  A "webstaffblocker", in my opinion, was some process or
function which worked fine in the old client but was completely broken or
missing in the new.  The translatability of these strings is certainly a
legitimate bug, but the issue is structural and transcends the particular
client (though the problem may be more exposed in the new client, I cannot
quite tell).

Any objections to removing that tag?  Then we can put 3.1 peacefully to
rest.  Bonus points for actually testing and signing off instead :)

Sincerely,
Dan


On Wed, Jul 22, 2020 at 3:19 PM Jason Stephenson <jason at sigio.com> wrote:

> Galen,
>
> I pretty much agree, though I would not have suggested one more release
> of 3.3. It is more than OK with me, though.
>
> I am also in favor of dropping 3.1, unless someone wants to maintain it.
> That someone not being me. :)
>
> I recently pushed the branch for https://bugs.launchpad.net/bugs/1886852
> to 3.4, 3.5, and master. If I had thought that 3.3 was still open for
> bug fixes, I would have pushed it there, too. I'm not sure how important
> people feel that fix is, though it would apply cleanly, except for a
> conflict with the version line 002.schema.config.sql.
>
> Cheers,
> Jason
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20200722/fd12e843/attachment-0001.html>


More information about the Open-ils-dev mailing list