[cle-release-team] [sakai2-tcc] CLE 2.9.4 vs CLE 2.10 effort

Neal Caidin neal.caidin at apereo.org
Fri Aug 30 09:39:49 PDT 2013


Looping back in the CLE release team so they can see Noah's substantive comments.

See below.

-- Neal



Neal Caidin
Sakai CLE Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Aug 30, 2013, at 11:58 AM, Noah Botimer <botimer at umich.edu> wrote:

> Oh, I like it just fine. But if we are remotely serious about some major changes, we should be conscious of a good time to make them and messaging around them. Something like 4.0 being "pretty much as things were" and 4.1 packing a bunch of dramatic changes is unhelpful for any involved. (5.0 would work.)
> 
> My principle here is that we should be planning two releases if these major things are any more than hot air. Whatever their versions are doesn't much matter to me, but there is an opportunity for adaptation and clear messaging of a maturity and process reboot, which we should not squander.
> 
> If we are just talking rather than positioning to implement major changes, same-as-ever works fine and the version is pretty irrelevant. It's all just v.latest.
> 
> Thanks,
> -Noah
> 
> On Aug 30, 2013, at 11:38 AM, Berg, Alan wrote:
> 
>> Still like 4. Like the Linux kernel. At a certain point you just have to say there is enough in there to warrant a major jump.
>> 
>> Noah Botimer <botimer at umich.edu> wrote:
>> 
>> Jokes and fun aside, please do not let us get whooped up over 4.0 branding yet. It's still just trunk until it's not.
>> 
>> I still favor some purposeful planning of a "get ready" release called 2.10 and a "whoa, lots of differences" release called 4.0.
>> 
>> My rationale is: there is a ton of stuff (without a good list) already in trunk without major restructuring, etc. There are things "on the roadmap" that might or might not come to be, like crazy portal cleanup, offloading of DB messaging and logging, major module restructuring, source control changes, build tool changes, better responsive support, and more. Holding the already-done stuff hostage for bold initiatives is not a victory for anyone. Charging forward with a mish-mash of a few known and a bunch of unknown things with a brand new 4.0 label is also not a victory. If there is a "marketing shot" to be fired, it should be better planned than "we're tired of calling it 2.x".
>> 
>> Thanks,
>> -Noah
>> 
>> On Aug 30, 2013, at 9:51 AM, Berg, Alan wrote:
>> 
>>> More that its functionality kicks ###
>>> 
>>> 
>>> 
>>> "Mark J. Norton" <markjnorton at earthlink.net> wrote:
>>> 
>>> Does that mean it's the last release?
>>> 
>>> - Mark
>>> 
>>> On 8/30/2013 9:36 AM, Berg, Alan wrote:
>>>> CLE 'Terminator' 4
>>>> 
>>>> 
>>>> Regards Alan,
>>>> 
>>>> Sent from somewhere interesting via a Mobile device.
>>>> 
>>>> 
>>>> 
>>>> -------- Original message --------
>>>> Subject: Re: [sakai2-tcc] CLE 2.9.4 vs CLE 2.10 effort 
>>>> From: Steve Swinsburg <steve.swinsburg at gmail.com> 
>>>> To: "Mark J. Norton" <markjnorton at earthlink.net> 
>>>> CC: sakai2-tcc Committee <sakai2-tcc at collab.sakaiproject.org> 
>>>> 
>>>> 
>>>> CLE 4  "Grilled Japanese Beef".
>>>> 
>>>> +1
>>>> 
>>>> 
>>>> On Fri, Aug 30, 2013 at 11:32 PM, Mark J. Norton <markjnorton at earthlink.net> wrote:
>>>> On 8/30/2013 9:18 AM, Anthony Whyte wrote:
>>>>> Sakai's La Rochelle menu (2011) [1]
>>>> 
>>>> Sign me up, I'm hungry already!
>>>> 
>>>> - Mark
>>>> 
>> 
> 
> _______________________________________________
> 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/cle-release-team/attachments/20130830/f17e1f02/attachment.html 


More information about the cle-release-team mailing list