[cle-release-team] 2.9.2 status check

Aaron Zeckoski azeckoski at unicon.net
Tue Apr 16 07:04:27 PDT 2013


I think these both should be merged. Why not merge a verified fix? Only
have my phone email today.
On Apr 16, 2013 9:38 AM, "Neal Caidin" <nealcaidin at sakaifoundation.org>
wrote:

>
> https://jira.sakaiproject.org/browse/KNL-1051 was verified, but maybe it
> would not hurt to be in trunk a little longer.  Perhaps some additional
> testing with changes to local properties, and make sure those behave as
> expected, would not be a bad idea. I definitely don't think we need to hold
> up CLE 2.9.2 for this one.
>
> https://jira.sakaiproject.org/browse/KNL-1038 - is listed as a blocker,
> but I don't understand it well enough to know for sure if it is serious
> enough to hold up the release. My guess is that it is not.
>
> 2 cents.
>
> If Matt is available to cut the RC01 today, that would seem like a good
> thing to me.
>
> It would be nice to hear other voices :-)
>
> Cheers,
> Neal
>
>
>
>
>
> On Apr 15, 2013, at 11:53 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
>
> > I don't think they need to hold up RC 01.  Whether they hold up 2.9.2 is
> for the release team to decide.
> >
> > I want to keep them on the radar since they are currently not flagged
> for 2.9.2 (other than a 2.9.2 triage label on at least one of the tickets).
> >
> > Anth
> >
> >
> > On Apr 15, 2013, at 11:47 AM, Neal Caidin wrote:
> >
> >> Which need to be addressed before the release, but not before RC01,
> correct?
> >>
> >> -- Neal
> >>
> >> On Apr 15, 2013, at 11:18 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
> >>
> >>> There are also permission back-fill conversion script issues raised by
> Chuck Hedrick that remain unresolved.
> >>>
> >>> https://jira.sakaiproject.org/browse/SAK-23471
> >>> https://jira.sakaiproject.org/browse/SAK-14373
> >>> both related to
> >>> https://jira.sakaiproject.org/browse/KNL-1024
> >>>
> >>> / Anth
> >>>
> >>>
> >>>
> >>> On Apr 15, 2013, at 11:02 AM, Neal Caidin wrote:
> >>>
> >>>> Good points Anthony. Thanks.
> >>>>
> >>>> Matt says he might be able to "cut" the release by tomorrow
> afternoon/evening (assuming things are ready and depending on his
> availability). That means one QA server - Longsight.
> >>>>
> >>>> Alan Berg says he will be available to configure his QA server on
> Wednesday. I haven't checked with Chuck H. yet.
> >>>>
> >>>> I'm finishing up the final details of the test plan. final-final
> details require the QA servers to be up and running.
> >>>>
> >>>>> From these data points, I'm guessing we will be able to start
> testing on Thursday, but there are still a few "hanging chads" (aka final
> details).
> >>>>
> >>>> FYI - My availability next week is spotty, unfortunately, including
> probably missing a 1/2 day Tuesday morning (Eastern Daylight), part of
> Wednesday afternoon, and then I'm unavailable Thursday, April 25 through
> April 29 (though I should be able to check in on things this day, at a
> minimum). I'm not sure how/if this will impact things.
> >>>>
> >>>> The sooner we can finalize things the better, so I can send out a
> call to the community asking for QA help.
> >>>>
> >>>> Cheers,
> >>>> Neal
> >>>>
> >>>> On Apr 15, 2013, at 10:37 AM, Anthony Whyte <arwhyte at umich.edu>
> wrote:
> >>>>
> >>>>> Down to 4 tickets at present, three of which are not ready to merge
> due to either missing info, merge conflicts or reversions due to problems.
>  Per the AntiSamy proposal we've got a day left before we are supposed to
> cut RC1.  I think we could live without both KNLs (never mind the SAKs).
> >>>>>
> >>>>> Are you guys comfortable with KNL-1051?
> >>>>>
> >>>>> Finally, I think emails such as this should be public and posted to
> the cle-release-team.  While I appreciate the politeness that no doubt
> serves as the motivation behind these private posts, I think we should talk
> about this stuff in public.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Anth
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Apr 15, 2013, at 7:51 AM, Neal Caidin wrote:
> >>>>>
> >>>>>> Hey guys,
> >>>>>>
> >>>>>> It seems like BLTI 2.1.0 is merged and I think so is AntiSamy ?
> >>>>>>
> >>>>>> It appears there are 1/2 dozen merges left, with one blocker:
> >>>>>>
> >>>>>> https://jira.sakaiproject.org/browse/KNL-1038
> >>>>>>
> >>>>>> Is this a true blocker for 2.9.2 or can we proceed without it, and
> fix for 2.9.3? If it gets fixed will we be ready to create RC01?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Neal
> >>>>>>
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> cle-release-team mailing list
> >>>> cle-release-team at collab.sakaiproject.org
> >>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> >>>
> >>
> >
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130416/398ea29d/attachment-0006.html 


More information about the cle-release-team mailing list