<div dir="ltr">thanks for that Gonzalo<div><br></div><div>the key version number criteria for marketing is not that it's a formal system, it's to simplify a story for people who have little or more likely no idea what Sugar is. The story we are developing is: we are meeting the challenge of handheld devices while supporting our 3 million Learners. This story will be well-served by a v2 or v3 number, but I'm afraid linking the year will box us into a timeframe when what we need (marketing standpoint again) is a version number on a flexible timetable according to circumstances.</div>
<div><br></div><div>F/LOSS projects are not a marketing reference for me, with very few exceptions they are not good at it at all. My references are the iPod, Nespresso, Amazon, Coca-Cola, etc.</div><div><br></div><div>Sean</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 7, 2013 at 10:47 PM, Gonzalo Odiard <span dir="ltr"><<a href="mailto:gonzalo@laptop.org" target="_blank">gonzalo@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sean,<br>
Usually, we are not doing big changes, but incremental changes.<br>
We are closer to the reality of the linux kernel, where the change to 3.0<br>
was not related to changes itself, but to the numbers where not comfortable,<br>
and they are planning release version 4.0 by the same reason in one year.<br>
<br>
What you think about using years as versions <a href="tel:%282013.1%202013.2" value="+12013120132">(2013.1 2013.2</a> or 13.1, 13.2)<br>
as a way to try incentive to the deployments and the final users<br>
to be updated?<br>
<br>
Gonzalo<br>
<div><div class="h5"><br>
On Thu, Nov 7, 2013 at 6:37 PM, Sean DALY <<a href="mailto:sdaly.be@gmail.com">sdaly.be@gmail.com</a>> wrote:<br>
> cc'ing marketing for... a marketing issue<br>
><br>
> Nope, the GTK3 change just passed under the radar. As stated previously I<br>
> lobbied for a v1 six years ago which is why we are ready for a v2. Or even a<br>
> v3.<br>
><br>
> For building a PR story I can work with v2 or v3, just not v1.<br>
><br>
> The issue with 2.2, 2.4 is that from a marketing perspective we get boxed<br>
> into a major number step timeframe irrespective of marketing needs. A major<br>
> number change should ideally happen when it's ready, or when we need to<br>
> communicate a major shift. I still think associating the existing numbering<br>
> behind a major number (e.g. 2.102) keeps continuity. PR will communicate the<br>
> major number, probably with a name. And not an unmarketable obscure name,<br>
> either.<br>
><br>
> Sean<br>
> Sugar Labs Marketing Coordinator<br>
><br>
><br>
><br>
><br>
> On Thu, Nov 7, 2013 at 8:36 PM, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> wrote:<br>
>><br>
>> Hmm I suppose the 1.x -> 2.x switch would have not made sense to marketing<br>
>> because there wasn't major user visible changes?<br>
>><br>
>><br>
>> On Thursday, 7 November 2013, Yioryos Asprobounitis wrote:<br>
>>><br>
>>><br>
>>><br>
>>> For sugar developers their is certainly a continuation in development and<br>
>>> the current numbering makes a lot of sense.<br>
>>> However, looking from outside 0.102 should be Sugar 3.x where 1.x is the<br>
>>> original, 2.x is the Gtk3/introspection move and now the html5/jc<br>
>>> (online/ultrabook/tablet) version.<br>
>>> If you actually consider 0.100 as 3.0 then it can go 3.2, 3.4 etc to keep<br>
>>> up with current numbering.<br>
>>> Should make marketing happy with minimal disruption.<br>
>>><br>
>>> _______________________________________________<br>
>>> Sugar-devel mailing list<br>
>>> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
>>> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>><br>
>><br>
>><br>
>> --<br>
>> Daniel Narvaez<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Sugar-devel mailing list<br>
>> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
>> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>><br>
><br>
><br>
</div></div>> _______________________________________________<br>
> Marketing mailing list<br>
> <a href="mailto:Marketing@lists.sugarlabs.org">Marketing@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/marketing" target="_blank">http://lists.sugarlabs.org/listinfo/marketing</a><br>
><br>
</blockquote></div><br></div>