On Friday, 28 September 2012, Walter Bender wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Sep 28, 2012 at 5:24 AM, Peter Robinson <<a href="javascript:;" onclick="_e(event, 'cvml', 'pbrobinson@gmail.com')">pbrobinson@gmail.com</a>> wrote: > On Wed, Sep 26, 2012 at 4:20 PM, Daniel Narvaez <<a href="javascript:;" onclick="_e(event, 'cvml', 'dwnarvaez@gmail.com')">dwnarvaez@gmail.com</a>> wrote: >> On 26 September 2012 16:02, Walter Bender <<a href="javascript:;" onclick="_e(event, 'cvml', 'walter.bender@gmail.com')">walter.bender@gmail.com</a>> wrote: >>> On Wed, Sep 26, 2012 at 9:48 AM, Daniel Narvaez <<a href="javascript:;" onclick="_e(event, 'cvml', 'dwnarvaez@gmail.com')">dwnarvaez@gmail.com</a>> wrote: >>>> On 26 September 2012 15:40, Walter Bender <<a href="javascript:;" onclick="_e(event, 'cvml', 'walter.bender@gmail.com')">walter.bender@gmail.com</a>> wrote: >>>>> Hmm. 100 is not large enough, whereas I am already up to Turtle Blocks v160 :P >>>>> But I don't know why even/odd is any less obvious than >< 100. >>>>> I am not sure how to proceed. >>>> >>>> Maybe start using dotted numbers for the gtk3 version only? >>> >>> That is an interesting idea. And as long as we list the dotted number >>> versions as 0.96+ then older Sugars will not look at them. So we could >>> have a whole number for gtk2 (< 0.96) and dotted number for gtk3. >>> Might work. But needs testing. >> >> As Gonzalo pointed out the problem is that latest sugar will see old >> gtk2 versions of the activity as newer than dotted recent ones. I'm >> getting convinced we should just use a very high version number (like >> 1000.0) to avoid that. Ugly but very straightforward. > > Maybe just use 100. > > From release 12 to 36 it's been a little over 2 years so at that rate > it's around 3 years until we reach 100 on gtk2. By then we should have > most end users above 10.1.3 and those that aren't are very unlikely to > be updating versions of Activities anyway so if we hit the 90s we can > go to dot releases. By them I hope gtk2 stuff is dead and we're all > just dealing with gtk3+ > > Peter I am not sure what problem we are trying to solve. If I give you any release number > than the latest gtk2 version, won't that solve your problem? And if I label that release with 0.96+ in ASLO, won't that resolve itself re old Sugar systems? I think the solution may lie in simply not making tar balls for gtk2 versions. </blockquote><div> </div><div>If, say, you release 50 for gtk3 and then 51 for gtk2, new systems will update to the gtk2 version. </div> -- Daniel Narvaez