[Building Sakai] [sakai-kernel] Version numbers.

Wed Feb 3 08:43:56 PST 2010

Yes, of course, sorry.

But in this case we might be looking at the wrong bit. The underlying problem is putting a number in the name...the '1' and '2' in K1 and K2.  I know that isn't a problem for the technical naming issue you're worried about but it will have communication/clarity implications. Personally, I think it isn't a disaster to let K1 go, say, from 1.11 to 1.12 even if there is an interruption in backwards compatibility. The number of people who need to worry about things like that is relatively small and we can handle the communication.  It is better, in my mind, than trying to explain the differences between K1 v2.0 and K2 v1.0 to those trying to get their arms around Sakai.

The only way out of this, long term, is to stop putting numbers into our release names. That gives the flexibility everyone wants. 
While I think it unlikely that K1 will undergo a *major* change (note I'm not disagreeing with David's point that narrow changes to backward compatibility are possible or even likely), the likelihood that K2 undergoes some substantial change in the next few years is substantially higher.  So we should imagine a K2 v2.0.  Below I said that would be K3, but now I'm not so sure. I guess I'd be interested in what people think about giving proper names to K1 and K2 and paying the communication cost now before we dig ourselves more deeply into the current structure. Even going to letters (SKA and SKB) would help matters.

So this is risking becoming a "what color should the bike shed" be conversation. But...WDYT? Should we find names for these things?

Michael

On Feb 3, 2010, at 06:50, David Horwitz wrote:

> Michael
> 
> for clarity the objection is not to having minor versions greater than 9
> but to have a situation where a change is introduced that requires a
> major revision for the version number to have any meaning, have to use a
> minor revision because otherwise there is a collision.
> 
> For code to use minor revisions it should be compatible with prior code.
> As a member of the maitanace team and the K1 team I cannot with any
> certainty say this wont happen before we EOL the K1 codebase (infact I
> would be suprised if we don't hit this sooner or later - just my gut feel)
> 
> D
> 
> On 02/03/2010 04:32 PM, Michael Korcuska wrote:
>> I agree with this.  K1 should go to 1.10 and then 1.11 and 1.12.  Likewise with K2.  And if we're building K2 v2.0 I think we would call it K3 v1.0.
>> 
>> Michael
>> 
>> 
>> On Feb 2, 2010, at 14:04, Ian Boston wrote:
>> 
>> 
>>> There are now 2 threads one here and one on sakai-kernel, it will be interesting to see if they come to the same conclusion.
>>> 
>>> K1 was originally Kernel 1.0 and
>>> K2 was originally Kernel 2.0
>>> 
>>> There is nothing to stop 1.x using 1.10 and beyond, in fact MediaWiki is currently at 1.15.1 see [1]
>>> 
>>> As a related issue, what happens to Sakai 2.x when it gets to 2.9 ? Calling it Sakai 3.0 is going to be very confusing.
>>> 
>>> Ian
>>> 
>>> 1 http://www.mediawiki.org/wiki/Download
>>> 
>>> On 2 Feb 2010, at 19:23, David Horwitz wrote:
>>> 
>>> 
>>>> Hi John,
>>>> 
>>>> Repeating the gist of my response to the k2 list here. I would think
>>>> that asuming there will never be a 2.0 release of the k1 kernel is a big
>>>> and dangerous assumption. I would recommend that the k2 group id not
>>>> collide with the k1 one.
>>>> 
>>>> David
>>>> 
>>>> On 02/02/2010 09:12 PM, John Norman wrote:
>>>> 
>>>>> Does the numbering affect K1 (e.g. by assuming K1 never gets to v2)? If so, we should probably ask on sakai-dev too...
>>>>> J
>>>>> 
>>>>> On 2 Feb 2010, at 18:54, Ian Boston wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> IHi,
>>>>>> 
>>>>>> In uploading the 0.2 artifacts to maven I have notices that the K1 kernel and K2 share the same group ID. This is probably correct but will create a problem when we get to the 1.0 release.
>>>>>> 
>>>>>> There are 2 options.
>>>>>> Change the groupId's
>>>>>> 
>>>>>> Skip all the 1.x versions and got to 2.0
>>>>>> 
>>>>>> eg 0.8,0.9, 2.0
>>>>>> 
>>>>>> WDYT?
>>>>>> Ian
>>>>>> 
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google Groups "Sakai Kernel" group.
>>>>>> To post to this group, send email to sakai-kernel at googlegroups.com.
>>>>>> To unsubscribe from this group, send email to sakai-kernel+unsubscribe at googlegroups.com.
>>>>>> For more options, visit this group at http://groups.google.com/group/sakai-kernel?hl=en.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>> 
>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>> 
>>>>> 
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>> 
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>> 
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>> 
>> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-- 
Michael Korcuska
Executive Director, Sakai Foundation
mkorcuska at sakaifoundation.org
phone: +1 510-859-4247 (google voice)
skype: mkorcuska