[Building Sakai] Fwd: K1 1.0.12: proposed kernel release (please review)

Anthony Whyte arwhyte at umich.edu
Fri Oct 9 12:49:18 PDT 2009


If KNL-210 is worth including in 1.0.12 for 2.6.1 I have no objections  
to merging the SAK-14165 fix into both the 2.6.1 release branch (now  
exists) and 2.6.x.

Cheers,

Anth


On Oct 9, 2009, at 3:40 PM, Matthew Jones wrote:

> KNL-210 has been running in production at Michigan for the past month
> as a local patch to 1.0.11 and we performed an internal review on it
> prior to release. The biggest improvements currently are to osp. I
> didn't know the kernel release schedule so held the related (also
> tested) SAK-14165 back from 2.6.1.
>
> On Fri, Oct 9, 2009 at 2:36 PM, Anthony Whyte <arwhyte at umich.edu>  
> wrote:
>> Beth would like to see KNL-210 in 1.0.12.  Reasons provided below.
>> Anth
>>
>> Begin forwarded message:
>>
>> From: Beth Kirschner <bkirschn at umich.edu>
>> Date: October 9, 2009 2:09:58 PM EDT
>> To: Anthony Whyte <arwhyte at umich.edu>
>> Cc: Horwitz David <david.horwitz at uct.ac.za>, Stephen Marquard
>> <stephen.marquard at uct.ac.za>, Eng Jim <jimeng at umich.edu>, Theriault  
>> Seth
>> <slt at columbia.edu>, Boston Ian <ian at caret.cam.ac.uk>, Davis Ray
>> <ray at media.berkeley.edu>
>> Subject: Re: K1 1.0.12: proposed kernel release
>> Hi Anthony,
>>
>>   I would like to see KNL-210 merged into the next kernel release  
>> -- without
>> it wait times for creating a portfolio could be several minutes  
>> long, and
>> people are seeing this outside of Michigan. I do _not_ feel  
>> comfortable
>> including KNL-253, however. There's no indication on the jira  
>> ticket that it
>> has received any level of testing/verification.
>>
>>   Binding the next kernel release to 2.6.1 seems reasonable tome.
>>
>> Thanks,
>> - Beth
>>
>>
>>
>> Begin forwarded message:
>>
>> From: Anthony Whyte <arwhyte at umich.edu>
>> Date: October 9, 2009 1:08:38 PM EDT
>> To: sakai-dev sakai-dev <sakai-dev at collab.sakaiproject.org>
>> Subject: [Building Sakai] K1 1.0.12: proposed kernel release  
>> (please review)
>> I am seeking comment on my proposal to release K1 1.0.12 (target  
>> date Monday
>> 12 Oct 2009).  There are currently 16 fixes in the 1.0.x branch  
>> that I would
>> like to leverage in the upcoming 2.6.1 release (links to filters  
>> below) as
>> well as the 2.6.x branch.  If not appropriate for 2.6.1 I'd like to  
>> put out
>> 1.0.12 and use it as the initial K1 version supporting 2.6.2 (e.g.  
>> bind
>> 2.6.x to it).
>> K1 1.0.12 closed issues (merged) (n=16)
>> http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12125
>> KNL issues linked to SAK issues
>> KNL-229 [cloned from SAK-16680]
>> KNL-219 SAK-7004 [closed, won't fix], SAK-16623 [duplicate]
>> KNL-175 [relates to SAK-11268 Stale Presence records need to be  
>> cleaned up
>> occasionally]
>> KNL-145 [cloned from SAK-13100]
>> I recommend that we restrict the release to these 16 fixes; there  
>> are four
>> other issues that could be merged to 1.0.x but I am currently of  
>> the opinion
>> that they should be bumped to a future maintenance release or  
>> excluded
>> entirely from 1.0.x.  The additional candidates include:
>> Closed Issues:
>> KNL-210 "Create variant of getResourcesOfType that restricts query to
>> specific site/contexts."
>> This fix introduces a CHS API change and perhaps is not appropriate  
>> for
>> 1.0.x releases.
>> Resolved Issues:
>> KNL-253 "Add smtp authentication and TLS to the kernel email  
>> component."
>> This fix is linked to KNL-283 "Add SSL connection capabilities to  
>> Email
>> service."  David Horwitz is of the opinion that neither of these  
>> fixes have
>> been tested sufficiently for inclusion in K1 1.0.12.
>> KNL-237 "DB2 - User search returns no results"
>> According to comments, this fix has yet to be verified against  
>> Oracle.
>> Open issue:
>> KNL-213 BaseResourceEdit return non url-encoded urls  (patch  
>> provided)
>> http://jira.sakaiproject.org/browse/KNL-213
>> IU has requested that this issue be addressed, however, the patch  
>> has yet to
>> be applied and David Horwitz is of the opinion that it will require  
>> a good
>> deal of testing before it goes into a release.  KNL-213 relates to  
>> SAK-16564
>> Syllabus gives a 404 when uploading a file with non-ascii
>> characters; http://jira.sakaiproject.org/browse/SAK-16564
>> Your judgements would be appreciated.
>> Anth
>> _______________________________
>> K1 1.0.12 closed issues (to merge) (n=1)
>> http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12132
>> KNL-210 Kirschner Create variant of getResourcesOfType that  
>> restricts query
>> to specific site/contexts
>> SAK-14165 "Portfolio assembly is slow with many completed  
>> Forms"depends on a
>> KNL-210 merge
>> K1 1.0.x resolved issues (to merge) (n=2)
>> http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12127
>> KNL-253 This patch adds smtp authentication and TLS to the kernel  
>> email
>> component.
>> KNL-237 DB2 - User search returns no results
>> _______________________________________________
>> 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"
>>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2417 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20091009/85385432/attachment.bin 


More information about the sakai-dev mailing list