[sakai2-tcc] CLE 2.9.4 vs CLE 2.10 effort

[Mark J. Norton]

 >  I do think it would be good to get some reaction to the community on 
any name change, just to be able to anticipate the response, if nothing 
else.

I was wondering why you think that donut or pudding names might be 
attractive to a Provost when pitching Sakai?  Personally, I think we 
should stay with the number system.  I prefer 4.0 since Sakai has made a 
lot of progress in the past few years.  The version numbers should 
reflect it's maturity, IMO.

I agree with Chuck, as well.  This release should have some major 
functional improvements.  Let's tackle some of the big ticket items that 
have languishing in Jira.  Also, give it a decent amount of time - a 
year at least.

That said, if you want to use code names for a release, then Sakai Maple 
Bacon, by all means!  Just release it as 4.0, please.

- Mark Norton


On 8/30/2013 8:14 AM, Neal Caidin wrote:
> AFAIK the TCC / PMC leanings are towards a number for the release. It 
> seemed to me like there was some momentum towards a Sakai 4, skipping 
> over Sakai 3 for the obvious (to this crowd) reasons. That being said, 
> I think donut flavor themes, not stores,  would be awesome! Sakai 
> Bavarian Creme, Sakai Raspberry Jelly, Sakai Maple Bacon. Mmmm mmm 
> good. Okay, I guess that is not *that* different from pudding themes.
>
> I do think it would be good to get some reaction to the community on 
> any name change, just to be able to anticipate the response, if 
> nothing else.
>
> Cheers,
> Neal "There-is-no-such-thing-as-a-bad-joke" Caidin
>
>
>
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
> Skype: nealkdin
> Twitter: ncaidin
>
>
>
>
>
>
>
>
>
> On Aug 29, 2013, at 11:50 PM, Charles Severance <csev at umich.edu 
> <mailto:csev at umich.edu>> wrote:
>
>>
>> On Aug 29, 2013, at 11:29 PM, Steve Swinsburg 
>> <steve.swinsburg at gmail.com <mailto:steve.swinsburg at gmail.com>> wrote:
>>
>>> Hi all,
>>>
>>> If we focus on 2.10 and don't have resources for a full 2.9.4 
>>> release at this time then we should continue to merge to 2.9.x where 
>>> appropriate - at some point in the future we could cut a 2.9.4 
>>> release. This goes directly to the goal that the branch is in a 
>>> constantly releasable state.
>>
>> This fits my thinking.  In effect we will almost certainly end up 
>> with a 2.9.4 one way or another - the question is it really just 
>> critical bug fixes that get merged or do we push non-trivial 
>> functionality into 2.9.4 like we have in 2.9.3 and 2.9.2.
>>
>> In particular if agree that the primary focus will be TimHorton (I 
>> decided to take names from famous donut shops) it does mean that 
>> moving bug fixes back might be a little trickier and trickier over time.
>>
>> For example once we decide that TimHorton is the focus - I will go in 
>> and drop all the 2.8 templates and skins i portal in trunk.  I might 
>> do a touch of code refactoring between SkinnableCharonPortal and 
>> PortalService - particularly those comments where we say "this code 
>> is duplicated in two other places..." - and I might just drop LTI 2.0 
>> into trunk of TimHorton with an experimental option to hide it 
>> instead of living in a Branch.
>>
>> All these things mean it gets harder and harder to push large amounts 
>> of code changes back to the 2-9-x branch since stuff gets pushed 
>> around and things are not even in the same places.
>>
>> It wont' be impossible to get a fix into 2-1-x just a little tricker 
>> potentially.
>>
>> I am for having a small fix-only 2.9.4 sometime in the future with a 
>> few months of making real progress on the trunk toward the TimHorton 
>> release.  For example, I would love to see someone drop in a non-db 
>> event bus and enable it buy default :)   Lets make some real progress.
>>
>> /Chuck
>
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130830/c547762a/attachment.html