Based on what I know today, I reluctantly vote against removal. There are some bugs in that list with no other current workaround except to use the xul client to perform an action. I would happily change my vote in a couple of weeks if more progress were made on some of the webstaffblockers.
Kathy -- Kathy Lussier Project Coordinator Massachusetts Library Network Cooperative (508) 343-0128kluss...@masslnc.org On Wed, Aug 29, 2018 at 11:57 AM Bill Erickson <beric...@gmail.com> wrote: > Devs, > > I'd like to have an informal vote on whether we should remove (well, > disable) the XUL client in 3.2. Delaying the decision is complicating the > release process. If it's clear which way the wind is blowing, we can set a > date for the final vote and patching. > > Knowing what you know today about outstanding webstaff blockers (a few > were just added), would you vote to proceed with XUL removal? Can I get a > show of hands, yea or nay? > > Thanks, > > -b > >
