[Marketing] [IAEP] [SoaS] Important Schedule Changes - Please Read!

[Sean DALY]

My main concerns are 1) contradicting our press releases and
journalist briefings (confusion is bad), 2) implying that SoaS is
classroom-ready (we're not there yet, we need teachers to pilot and
send feedback).

Simon - actually for me the SoaS timetable has always been linked to
the Fedora timetable... but SoaS v1 on F12 not F11... to give
ourselves time to test hardware (transmitting info to Fedora) and thus
flesh out a list of confirmed working machines, and to build up
related support (website, feedback handling, marketing materials for a
major press launch).

The goal behind "beta-1", "beta-2" (or "RC" which is better), "v1" is
to use instantly understandable numbering for nontech observers and
prospective Sugar deployers (teachers, parents, journalists),
benefiting from a grace period during "beta" phase (you've noticed no
journalists knocking it... yet) and working up to v1 in an announced
timeframe (when journalists will feel free to knock it, but we will be
better prepared too). Numbering successive versions with the "F-11"
formula is a good approach I think.

The SoaS strategy is I think the right one for getting Sugar into classrooms.

Sean






On Wed, May 27, 2009 at 12:16 AM, Bernie Innocenti <bernie at codewiz.org> wrote:
> On 05/26/09 20:36, Caroline Meeks wrote:
>> Here is what I see.
>>
>> V1 has a meaning to open source developers that you believe is going to
>> be accurate in June.  (I don't really get how SoaS needs to be V1 if
>> Sugar is still in point releases though).
>
> Look at OLPC: they've already reached version 802.  Jeez, we'll never
> catch them without inflating our release numbers too! ;-)
>
> Seriously, no software is ever finished nor perfect, therefore by
> applying a honest quality metric on release numbers no one would ever
> reach V1.0.
>
> I propose labelling our first formal release, regardless of perceived
> quality, "SoaS 1" (or "SoaS 2009.8", or even "SoaS Nerdy Nipples", if
> you prefer).  The next one would be called SoaS 2, and so on.  Our
> upstream Fedora has been doing this for 6 years now.
>
> We can always add the necessary caution notices in the release notes, of
> course.
>
> --
>   // Bernie Innocenti - http://codewiz.org/
>  \X/  Sugar Labs       - http://sugarlabs.org/
>