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

[David Horwitz]

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"
>>     
>