[OPEN-ILS-GENERAL] Evergreen: supported releases policy (request for feedback)

[Soulliere, Robert]

Hi All,

I strongly agree with this supported releases policy and I think that the downloads page needs to reflect this policy so that the current releases are listed and understood to be the ones users should install.

This policy will make life easier for developers the documentation team and users.

I had one question regarding naming conventions and releases of non-publicized releases (e.g. 1.6.2.0). Could we have a naming convention for unofficial/untested/temporary releases. I think I understand as to how and why 1.6.2.0 came about but remains in unofficial territory, but I wonder if we  could add a code to its label/version to indicate that it is unofficial? I understand that it can be kept in the closet and unadvertised, but I am left with a bit uneasiness in its label. From a casual user or outsider, 1.6.2.0 sound like a nice upgrade to 1.6.1.5. Could it be labelled with something like 1.6.2.0_NR to indicate that it is a non-release? The code could be something else such as "SR" for special release, "UR" for unofficial release, etc.., but alpha characters after the version number might help to raise red flags for users that this is outside of the upgrade cycle or that upgrading is "at your own risk". This could work the same way alpha, beta, and RC labels work to let uses know that it might not be ready for a live environment.

I also agree with the point that user who want future enhancements should be looking at the Evergreen 2.x series and that developer time should be invested in the 2.x or latest releases and not invested in back porting new features for old versions. I understand that certain circumstances may force new features to appear in older version releases, but should be avoided if at all possible. It just seems like a practice that will make development a bit less complicated.


Thanks,
Robert

Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
robert.soulliere at mohawkcollege.ca
Telephone: 905 575 1212 x3936
Fax: 905 575 2011
________________________________________
From: open-ils-general-bounces at list.georgialibraries.org [open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Dan Scott [dan at coffeecode.net]
Sent: December 21, 2010 11:37 AM
To: Evergreen Discussion Group
Subject: [OPEN-ILS-GENERAL] Evergreen: supported releases policy (request       for feedback)

As one of the development team's efforts to provide clearer communication
and to set expectations for community support for Evergreen, I have
written a draft "Supported releases" policy that defines what the
development team plans to support over time:
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:evergreen:supported_releases

Perhaps the most pertinent two sentences are:

"""
The Evergreen development team shall support the last two concurrent
minor releases ("supported releases"). "Support" is defined as fixing
bugs that are reported and which can be reproduced in the supported
releases."
"""

If you are interested in this policy, please read the draft policy
in full and provide feedback as a response to this message on the
Evergreen General Discussion mailing list.

Thanks,
Dan

This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message.  If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited.  If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.