[cle-release-team] Off cycle kernel release possible?

[Steve Swinsburg]

They wouldn't have incorrect fix version, the items already in the branch would be included in 1.3.2.

Unless you meant he take the current 1.3.1, merge in only his fix, and release. Though D mentioned taking a cut of the current branch. 

I say go for it, release the branch. Might as well include a few extra merges as Anth metioned. 

Change the version in 2.9.x when done to point to the new kernel version. 

Cheers
Steve

Sent from my iPhone

On 28/03/2013, at 3:11, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> I think 1.3.2 is the version planned to coincide with 2.9.2. Though we
> could break out of that numbering it would mean a lot of JIRAs have
> wrong fix versions.
> -AZ
> 
> 
> On Wed, Mar 27, 2013 at 12:08 PM, David Horwitz <david.horwitz at uct.ac.za> wrote:
>> I would call it 1.3.2 which would be consistent with past practice. But yes basically a properly versioned release of the current kernel 1.3.x branch as it stands now ...
>> 
>> 
>> D
>> 
>> Sent from my iPad
>> 
>> On 27 Mar 2013, at 18:03, "Aaron Zeckoski" <azeckoski at unicon.net> wrote:
>> 
>>> Link to the JIRA
>>> https://jira.sakaiproject.org/browse/KNL-1037
>>> 
>>> So you want to do a 1.3.1.1 with just the changes from that ticket?
>>> https://source.sakaiproject.org/svn/kernel/tags/kernel-1.3.1/
>>> 
>>> Or just a current version of the 2.9 kernel (which includes it).
>>> Because I think an RC is planned for a week or two from now.
>>> -AZ
>>> 
>>> 
>>> 
>>> On Wed, Mar 27, 2013 at 10:46 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
>>>> Hi Gang,
>>>> 
>>>> Not knowing the current state of the  process I have a question - Would an
>>>> off cycle of the kernel be possible?
>>>> 
>>>> We need to KNL-1037 in production and I want to avoid msubing the kernel
>>>> again.
>>>> 
>>>> regards
>>>> 
>>>> David
>>>> 
>>>> ________________________________
>>>> UNIVERSITY OF CAPE TOWN
>>>> 
>>>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer
>>>> published on our website at
>>>> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27
>>>> 21 650 9111. This e-mail is intended only for the person(s) to whom it is
>>>> addressed. If the e-mail has reached you in error, please notify the author.
>>>> If you are not the intended recipient of the e-mail you may not use,
>>>> disclose, copy, redirect or print the content. If this e-mail is not related
>>>> to the business of UCT it is sent by the sender in the sender's individual
>>>> capacity.
>>>> 
>>>> 
>>>> _______________________________________________
>>>> cle-release-team mailing list
>>>> cle-release-team at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>> 
>>> 
>>> 
>>> --
>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>> ________________________________
>> UNIVERSITY OF CAPE TOWN
>> 
>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.
>> 
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 
> 
> 
> -- 
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team