[OPEN-ILS-GENERAL] Release manager / management / process? (was: Official EOL Policy)

[Stephen Wills]

A quick glance at the wiki revealed some pretty good documentation on  
how to release and test.   There are some missing volunteer names next  
to 2.1 and, as usual, the indexing could be a little better.  All in  
all, I would agree that there is little for an RM to shake his stick  
at conceptually.


On Dec 22, 2011, at 11:20 AM, Dan Scott wrote:

> On Tue, Dec 20, 2011 at 03:38:45PM -0600, Anoop Atre wrote:
> <snip>
>> Maybe what we need to plan next is a release manager with a big  
>> stick?
>
> [snip]

Maybe the following ideas could be added to an 'ideas for improving  
process' page.
Happy to start that if seems it might be useful?

> Perhaps, in addition to the to-be-written Evergreen release cycle
> document, we could articulate the general goals that we want to  
> achieve for
> a given release (e.g. "Supports a clean upgrade from previous  
> release",
> "Maintains or improves performance over the previous release, broken
> down by 1. search, 2. circulation speed, 3. etc", "Offers a fully
> translated public interace in the following locales", "All new  
> features
> have an overview in Release Notes and more detailed documentation in  
> the
> manual", etc). Then, after each release, we could do a "quick"  
> evaluation
> (hah) and post-mortem to see where we fell short of our goals, and  
> come
> up with ideas on how to address those shortcomings in the next  
> release.
>
> Anything we do depends heavily on buy-in from contributing parties,
> of course.
>