[sakai2-tcc] [maint] Maintenance Branches: Enhancement vs Bug Merges

[Noah Botimer]

To front-load my support, +1. If you can't tell me how to test it, I'm not convinced it's modest or fully understood -- thereby violating my concept of our promise of what maintenance releases mean.


So, for more...

I don't think that it's too much to ask to have these exceptional cases (5-10 a year?) documented in a standard form, including a few words of how to verify them. Our JIRA tickets are just too numerous and inconsistent to use as a real feature list.

The goal isn't to be a barrier; it's to spend about 10-20 minutes up front to explain out-of-band features and save the puzzlement and frustration of mysterious changes. These might not be right for the job, but perhaps these templates could be inspiration for a lightweight tool:

http://confluence.sakaiproject.org/display/OSP/OSP+Feature+Template
http://confluence.sakaiproject.org/display/OSP/OSP-SPEC+-+Specification+Template


A few completed examples (for admittedly more involved features than we might expect in maintenance):

http://confluence.sakaiproject.org/display/OSP/Evaluator+Selection+Redesign
http://confluence.sakaiproject.org/display/OSP/Duplicating+portfolios
http://confluence.sakaiproject.org/display/OSP/Indiana+University+Matrices+Enhancements
http://confluence.sakaiproject.org/display/OSP/Collaborative+Portfolio+Contributions

Thanks,
-Noah

On Dec 8, 2010, at 2:58 PM, Beth Kirschner wrote:

> I believe the intent is that the institution doing the merge is responsible for testing. Perhaps we could require a Test Plan be documented and followed in the JIRA?
> 
> - Beth
> 
> On Dec 8, 2010, at 2:48 PM, Seth Theriault wrote:
> 
>> Beth Kirschner wrote:
>> 
>>> - The change must be QA tested with the maintenance branch 
>>> before the merge
>> 
>> I'd like to hear whether QA and RelMgmt thinks they have the 
>> capacity to support this condition given that we are currently 
>> maintaining and/or testing up to a half-dozen "releases" at a 
>> time (currently 2.6, 2.7, 2.8, plus their respective kernels) 
>> plus the indies.
>> 
>> Seth
>> 
>> 
>> 
> 
> 
>