[OPEN-ILS-GENERAL] Testing the new XULRunner branch

[Kathy Lussier]

Thanks Lindsay!

As the 2.3 release manager, Bill Erickson may be a better person to speak to this question. However, my understanding is that the 2.3 beta feature freeze is on August 1, and, at that time, no new features can be added to 2.3. 

Given that timeframe, I think it would be good if testing of the new XULRunner code could be done this week. 

Kathy

-------------------------------------------------------------
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
klussier at masslnc.org
IM: kmlussier (AOL & Yahoo)
Twitter: http://www.twitter.com/kmlussier
 
 


>>-----Original Message-----
>>From: open-ils-general-bounces at list.georgialibraries.org [mailto:open-
>>ils-general-bounces at list.georgialibraries.org] On Behalf Of Lindsay
>>Stratton
>>Sent: Monday, July 23, 2012 9:20 AM
>>To: Evergreen Discussion Group
>>Subject: Re: [OPEN-ILS-GENERAL] Testing the new XULRunner branch
>>
>>Is there a particular time frame for testing? I'd be more than happy to
>>test circulation functions, but have a few time constraints.
>>
>>Lindsay Stratton
>>Training Coordinator
>>Pioneer Library System
>>2557 State Rte 21
>>Canandaigua, NY 14424
>>
>>http://www.pls-net.org
>>
>>
>>
>>________________________________
>>
>>
>>	From: "Kathy Lussier" <klussier at masslnc.org>
>>	To: "Evergreen Development Discussion List" <open-ils-
>>dev at list.georgialibraries.org>, open-ils-
>>general at list.georgialibraries.org
>>	Sent: Thursday, July 19, 2012 2:12:50 PM
>>	Subject: [OPEN-ILS-GENERAL] Testing the new XULRunner branch
>>
>>	Hello Evergreen community!
>>
>>	Please excuse cross postings.
>>
>>	Several months ago, Thomas Berezansky at MVLC submitted code to
>>support
>>	Evergreen on newer versions of XULRunner. Jason Stephenson has
>>written a
>>	great blog post about why this code is important at
>>	http://blog.mvlcstaff.org/2012/05/testing-1-2-3.html. In addition
>>to
>>	providing more longevity for the Evergreen staff client, it also
>>has the
>>	potential to improve performance.
>>
>>	With the 2.3 beta feature freeze coming soon, I'm concerned that
>>the
>>	code might not get enough testing to get the sign off to be
>>merged into
>>	2.3.  Unlike other development branches, this code requires
>>testing in
>>	all parts of the staff client and really shouldn't be left to one
>>	person. The more testers we have, the less likely we are to see
>>bugs
>>	when this code is eventually merged. To help with recruiting
>>volunteers,
>>	I have posted a page at
>>	http://open-ils.org/dokuwiki/doku.php?id=qa:new_xul_testing where
>>	volunteers can sign up to test various areas of the staff client.
>>I have
>>	already tested the MARC batch import interface and have
>>volunteered to
>>	review acquisitions as well. However, it wouldn't hurt if others
>>were
>>	willing to test those areas as well.
>>
>>	Testing does not need to be limited to developers. Thomas has
>>made it
>>	really easy to test this branch. He has set up a server running
>>master
>>	that also has the new XULRunner code loaded. Details for
>>downloading a
>>	client and logging into this server are available at
>>	https://bugs.launchpad.net/evergreen/+bug/942134/comments/1.
>>Jason's
>>	blog post also provides details on how you can load the branch on
>>to
>>	your own testing server.
>>
>>	If you find any bugs unique to the new XULRunner branch, you can
>>report
>>	them on the Launchpad bug at
>>	https://bugs.launchpad.net/evergreen/+bug/942134. It also might
>>be a
>>	good idea to report any successful testing here so that we know
>>that a
>>	function has been tested successfully.
>>
>>	I hope many of you consider helping out with this effort. It's a
>>great
>>	way to make a tangible contribution to the Evergreen community!
>>
>>	Kathy
>>
>>	--
>>	Kathy Lussier
>>	Project Coordinator
>>	Massachusetts Library Network Cooperative
>>	(508) 756-0172
>>	(508) 755-3721 (fax)
>>	klussier at masslnc.org
>>	Twitter: http://www.twitter.com/kmlussier
>>
>>
>>