[cle-release-team] Name for current testing cycle for Sakai 10?
Noah Botimer
botimer at umich.edu
Wed Nov 20 12:35:06 PST 2013
I don't think we've taken a lot of value from our past slushies. When QA activity starts happening against a branch as opposed to trunk, we should just be clear that things have flipped -- the branch is for QA on fixes for the imminent release, while new stuff goes in trunk. I don't think anyone will be surprised or have difficulty with that.
Contrast that with "right now", which should be "new stuff is not welcome in trunk, build in a branch and keep up to date as you see fit".
"Code freeze" just doesn't seem like a useful moment/distinction/term in most modern development, especially so in distributed/open development. I think it's gone the way of the waterfall.
By the way 1, I think this aligns quite well with DVCS principles used in other big projects. There is a period when "master" is the leading/bleeding edge, then there is a period where it's stable and being incremented with small bits, then there is a period where some people want to move forward and do so in a branch while others continue to polish the stable master, then there is a moment when stable goes into a maintenance branch and the future branch goes into master, then it repeats.
By the way 2, I do think there is value in declaring what you're working on that you hope would be in a future release, and coordinating the start of QA cycles with that -- but that is an 11 conversation at the moment, not a 10 conversation. Effectively any new stuff should be in branches right now.
Thanks,
-Noah
On Nov 20, 2013, at 8:49 AM, Neal Caidin wrote:
> I can live with that, though I have a preference for somehow demarking when we have a code freeze. I don’t think the QA testers will care either way.
>
> I suppose this is something we can just do and not need a broad discussion about, since it is purely administrative and does not affect scope, schedule, testing etc.
>
> Once we cut a release, I’ll call it qa01 and we will iterate. I imagine code freeze will probably happen at qa02, but maybe qa03.
>
> Cheers,
> Neal
>
>
>
> Neal Caidin
> Sakai Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
>
>
>
>
>
>
>
>
>
> On Nov 20, 2013, at 8:22 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
>
>> Agreed.
>>
>> anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu | 517-980-0228
>>
>>
>> On Nov 20, 2013, at 12:07 AM, Steve Swinsburg wrote:
>>
>>> It would be easier to read and track if you had sakai-10.0-qa1, sakai-10.0-qa2 etc. We know what rev each tag was created at.
>>>
>>> cheers,
>>> Steve
>>>
>>>
>>> On Wed, Nov 20, 2013 at 3:19 AM, Neal Caidin <neal.caidin at apereo.org> wrote:
>>> What if we used revision tags for qa names?
>>>
>>> sakai-10-131740 (current revision number of trunk) , sakai-10-131772 (making this up for illustration purposes), etc, until we reach RC tag?
>>>
>>> What do you think of that? It might help us keep track of which bugs occur on which revisions. I think it still captures the simplicity you are after?
>>>
>>> If I put out a call for testing right now, I guess I will just do it to the QA and Dev lists and say we are testing trunk, in preparation for Sakai 10 being “cut”. I would just label my current documents as Sakai 10 Trunk testing.
>>>
>>> ?
>>>
>>> Thanks!
>>>
>>> Neal
>>>
>>>
>>>
>>> Neal Caidin
>>> Sakai Community Coordinator
>>> neal.caidin at apereo.org
>>> Skype: nealkdin
>>> Twitter: ncaidin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Nov 19, 2013, at 10:24 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
>>>
>>>> "Prep phase" - no.
>>>>
>>>> As for objections, for me alpha vs beta phasing is largely a fiction. The only measurable distinction between the two terms is that alpha is unlikely to be feature complete. Beta by implication is feature complete (frozen) but is likely to include blockers. But again, counting blocker vs non-blocker tickets in Jira is not exactly a rigorous measure of defect reduction.
>>>>
>>>> I suggest we just tag the QA tags as sakai-10.0-qa01, 02, 03, 04 (or append the revision to the tag name, e.g., sakai-10.0-qa01-r123456) . . . until we we are ready to issue an RC tag. Simple.
>>>>
>>>> If you consider absolutely necessary to provide a name for the period between now and the day that trunk is branched to 10.x, call it alpha.
>>>>
>>>> Anth
>>>>
>>>>
>>>> anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu | 517-980-0228
>>>>
>>>>
>>>> On Nov 19, 2013, at 9:38 AM, Matthew Jones wrote:
>>>>
>>>>> I don't remember any objections to alpha, though we aren't technically in alpha yet, as there hasn't really even been a release made.
>>>>>
>>>>> I'm guessing we'd go through similar phases and create alpha1, alpha2 releases and jira versions etc once all of the blockers are resolved.
>>>>>
>>>>> Really the blockers just involve removing the sections and gradebook standalone (sections is done just not committed, gradebook is more involved but possibly this week) and also testing the conversion scripts. I had a lot of errors in the mysql script and had to start off a fresh database.
>>>>>
>>>>>
>>>>> On Tue, Nov 19, 2013 at 9:26 AM, Neal Caidin <neal.caidin at apereo.org> wrote:
>>>>> [
>>>>> Hi All,
>>>>>
>>>>> Does anybody have a preference for what we should call the pre-Beta testing cycle for Sakai 10 ? I think I’ve heard objections to calling it Alpha, but I’m hoping to start drumming up testers and it would be nice to have something simple to call it, just for administrative purposes. Plus I’m naming the Google docs and the Confluence pages, etc. Need something to tie it all together.
>>>>>
>>>>> I thought of “Prep phase”, but I’m not liking it. Ideas?
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Neal
>>>>>
>>>>>
>>>>>
>>>>> Neal Caidin
>>>>> Sakai Community Coordinator
>>>>> neal.caidin at apereo.org
>>>>> Skype: nealkdin
>>>>> Twitter: ncaidin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cle-release-team mailing list
>>>>> cle-release-team at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cle-release-team mailing list
>>>>> cle-release-team at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>>
>>>
>>>
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>
>>>
>>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131120/c213806a/attachment.html
More information about the cle-release-team
mailing list