Re: [OPEN-ILS-DEV] Supported releases

2020-07-23 Thread Galen Charlton
Hi, On Thu, Jul 23, 2020 at 9:34 AM Galen Charlton wrote: > - remove the 3.1.8 milestone in LP > I meant 3.3.8, of course. In any event, that milestone is now gone. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS

Re: [OPEN-ILS-DEV] Supported releases

2020-07-23 Thread Galen Charlton
Hi On Thu, Jul 23, 2020 at 9:02 AM Daniel Wells wrote: > Based on feedback here and on the bug as well, I have removed the > webstaffblocker tag. Better throw that 3.1 retirement party quick before > another blocker pops up ;) > Looks like we have a consensus. Based on that, I'm going to take

Re: [OPEN-ILS-DEV] Supported releases

2020-07-23 Thread Daniel Wells
Based on feedback here and on the bug as well, I have removed the webstaffblocker tag. Better throw that 3.1 retirement party quick before another blocker pops up ;) Dan On Wed, Jul 22, 2020 at 5:44 PM Bill Erickson wrote: > +1 saying goodbye to 3.1, 3.2, and 3.3. > > I also agree the

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Bill Erickson
+1 saying goodbye to 3.1, 3.2, and 3.3. I also agree the webstaffblocker tag should not have been applied to 1773191 . -b On Wed, Jul 22, 2020 at 4:00 PM Jason Boyer wrote: > I would agree that tag should never have been applied to that bug

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Jason Boyer
I would agree that tag should never have been applied to that bug since as you mentioned, things were no different in the xml client. With that tag removed we can let the sun set on 3.1 and hopefully that branch will make a nice incentive to upgrade to 3.6. :) Jason -- Jason Boyer Senior

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Jason Boyer
I’m for removing all support for 3.1, especially since the xulrunner client has become essentially unusable with TLS certificates that have StartCom in their trust chain. That's not going to get any better. I don’t know how important it is to release a 3.3.8. The 6 commits between rel_3_3_7

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Daniel Wells
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

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Blake Henderson
+1 to dropping 3.1 and 3.2 and 3.3. Thanks Galen for updating that page. I was just thinking about this myself yesterday! Good timing! -Blake- Conducting Magic Can consume data in any format MOBIUS On 7/22/2020 1:52 PM, Jane Sandberg wrote: My preference would be to keep things simple, and

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Jason Stephenson
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

Re: [OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Jane Sandberg
My preference would be to keep things simple, and drop all but 3.4 and 3.5. But if others would find additional 3.3 (or possibly 3.1) releases helpful, I could be persuaded. On Wed, Jul 22, 2020, 11:30 Galen Charlton wrote: > Hi, > > I've updated the list of supported releases at > >

[OPEN-ILS-DEV] Supported releases

2020-07-22 Thread Galen Charlton
Hi, I've updated the list of supported releases at https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule 3.3 has technically hit end of life for both features and security fixes, but I have a mild itch to suggest that we do a final release of 3.3.8 to scoop up the various