Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond

2017-08-03 Thread Forrest, Stuart
-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Boyer, Jason A Sent: Thursday, August 03, 2017 12:11 PM To: Evergreen Development Discussion List Subject: Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond +1 From me. -- Jason Boyer MIS Supervisor Indiana State

Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond

2017-08-03 Thread Galen Charlton
Hi, On Thu, Aug 3, 2017 at 11:40 AM, Kathy Lussier wrote: > This was briefly discussed during yesterday's meeting, but to properly > identify these showstopper issues, should we be setting showstopper web > client bugs to a priority of 'high' in Launchpad? Or is there

Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond

2017-08-03 Thread Boyer, Jason A
een Development Discussion List d...@list.georgialibraries.org> > Subject: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond > > This is an EXTERNAL email. Exercise caution. DO NOT open attachments or > click links from unkno

Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond

2017-08-03 Thread Kathy Lussier
+1 from me too, with a couple of follow-up questions/comments: Of course, a strict interpretation of this policy presumes that showstopper issues with the web staff client are addressed by 3.0.0, or at least early in the 3.0.x maintenance release cycle. This was briefly discussed during

Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond

2017-08-03 Thread Jason Etheridge
+1 from me as well :) -- Jason Etheridge Community and Migration Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: ja...@equinoxinitiative.org web: http://EquinoxInitiative.org

[OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond

2017-08-02 Thread Galen Charlton
Hi, Following the discussion during the development meeting today, here's a draft of a policy on merging XUL bugfixes once 3.0 is released, in conjunction with the planned deprecation of the XUL staff client: START Starting with the release of 3.0.0, patches that fix XUL bugs will not