[OPEN-ILS-DEV] Release process & QA thoughts

[Almond, Emily]

You're both hitting on some best practices of software development...
part of my job right now is to survey the landscape and figure out
what's being done right, wrong, or not at all. Your comments are very
helpful in determining where to start!

 

In the coming weeks, I'll be talking to folks around Georgia and at
Equinox in order to develop out both a product lifecycle and a project
lifecycle. Under both, respectively, and with much input from the PINES
libraries, we'll need to answer the following questions:

1.       What belongs in the product lifecycle (i.e., maintenance)?

2.       What belongs in a release cycle?

3.       What belongs in an upgrade cycle?

4.       How do we define the criteria for categorizing? (is it a bug,
showstopper, something in between?)

5.       How to form a group of "beta testers" (release candidates)?

6.       Form communication plans around each group.  (betas, sys
admins, directors, Equinox, library users, both internal and external)

7.       Identify and implement the most appropriate and efficient
communication channels - listservs, discussion forums, chat logs,
virtual meeting spaces, wikis, etc.

 

As I cobble these and other questions and issues together into a plan, I
will be posting regular updates to the PINES page and will be conducting
many site visits in the coming months. So keep discussing!

Emily

 

From: open-ils-dev-bounces at list.georgialibraries.org
[mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of
Warren Layton
Sent: Monday, October 27, 2008 7:21 AM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] Release process & QA thoughts

 

On Sun, Oct 26, 2008 at 4:34 PM, Dan Scott <denials at gmail.com> wrote:

	I would like to put forward a suggestion that no major release
(x.y.0
	in the case of OpenSRF or x.y.z.0 in the case of Evergreen)
should
	ever go out without at least one release candidate.


Yes please! I'm one of those people that enjoys grabbing the latest
release candidate, giving it a spin, and, if possible, providing a bit
of feedback. 

 

	I would also like to propose more open communication about
upcoming
	releases on the -dev list to help coordinate efforts.

 
I like this idea as well. I know the core developers are on IRC and that
chatting is a very efficient way for them to coordinate their efforts.
However, the -dev list could be used to give keen non-core people some
clues about how the release is coming along and when it is expected to
land. At the very least, it's quicker and easier to get this type of
info by browsing through mail archives than scanning through IRC logs.

Cheers,
  Warren

 

 

Emily A. Almond

PINES Software Development Manager

Georgia Public Library Service

1800 Century Place, Suite 150

Atlanta, GA 30345-4304

(404) 235-7149.tel

(404) 235.7201.fax

ealmond at georgialibraries.org

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20081027/183151d6/attachment-0001.htm