[sakai2-tcc] Summary of meeting - Re: TCC - CLE coordinator meeting - Wednesday, Oct 31, 8 am EDT (12 pm GMT)
Noah Botimer
botimer at umich.edu
Wed Oct 31 09:38:44 PDT 2012
I am in support of a full speed ahead approach for 2.9.0.
There are some issues outstanding, and those deserve to be addressed (fixed
or expressly deferred). I think the best thing for the product, community
health, and overall coordination is to get into a pattern of releasing
rather than delaying.
All releases will have flaws. Adopters realize this and will appreciate
clear milestones, as opposed to an indefinite and incomprehensible "almost
there" state. They will decide if they are ready to adopt any given
release, provided we are transparent about what's in it or not. The
"everyone runs a maintenance branch anyway, so we don't really need
releases" status quo is an abomination. It is also a fallacy that delaying
a release will cause better QA and more fixes -- experience shows us in our
community that releases drive reporting, QA, and fixes more than potential
releases do.
Here is my recommendation (given that it appears the short list is at one
issue):
1. Pick a release date that affords time for the mechanics of
releasing and verifying artifacts.
2. Touch base with QA contacts for "last call" show stoppers. If
any come, make a time-limited call for CLE team / TCC input about direction
or resolution. Default to releasing in absence of a majority vote to delay.
3. Compile release notes with a list of known issues (of sufficient
severity, probably defined as Critical+ JIRA issues affecting the RC).
4. Draft a specific timeline for 2.9.1, addressing some portion of
the known issues and others arising.
5. Release 2.9.0 with specific mention of the known issues and
intent to release 2.9.1 on the above schedule with as many issues addressed
as resources allow. Remind everyone in the notes that issues discovered
should be reported and offer an open inbox for reporting issues as to help
those who do not understand the JIRA process get started.
6. Execute 1-5 for 2.9.1 and repeat with decreasing frequency as
important issues are resolved and focus shifts to 2.10.
I do recognize that this is a plan with no backing resource on my behalf.
Please consider it as what I see as a plan for moving us toward a series of
successes, as opposed to languishing so near the finish line. Nothing more.
Thanks,
-Noah
On Wed, Oct 31, 2012 at 11:18 AM, Neal Caidin <
nealcaidin at sakaifoundation.org> wrote:
> Attending: Aaron Z, Jean-François L, Alan B, Megan M, Anthony W, Neal C
>
> CLE 2.9.0 - Without a transcript, it would be difficult to capture the
> conversation from this morning, so this is just a high level summary. Most
> of the discussion was around the 2.9.0 release and whether we will have a
> good enough quality release to proceed and the balance of that compared to
> the risk of not releasing now, which would push the 2.9.0 release date to
> December at best, and the possibility of sliding into 2013. Anthony brought
> in the OAE perspective and the risk of how Sakai might be viewed overall in
> light of OAE struggles and 2.9.0 delays, but still with an appreciation for
> the need of a quality release.
>
> Mobile update - not much discussion other than what is in notes. Mostly
> tone seems to be a wait-and-see how things develop. Keep an eye on it. I
> did mention that initial funding for this effort has already been procured.
>
> Presentation for Educause - one, imho, great piece of feedback, to include
> a slide encouraging community participation and how folks can get engaged.
> I will make sure to include something like that. I'm confident Ian D. and
> Chuck S. would agree.
>
> Thanks,
>
> Neal Caidin
>
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
>
>
>
>
> On Oct 31, 2012, at 7:44 AM, Neal Caidin <nealcaidin at sakaifoundation.org>
> wrote:
>
> > Ping.
> >
> > 8 am Eastern Daylight, 12 pm GMT , TCC meeting.
> >
> > Th
> > On Oct 30, 2012, at 2:38 PM, Neal Caidin <nealcaidin at sakaifoundation.org>
> wrote:
> >
> >> Reminder, early morning 8 am meeting Eastern Daylight. 5 am for West
> Coast folks? ;-) If you are from the West Coast and attend, I'll buy you a
> cookie.
> >>
> >> [sorry for the lengthy email. I guess a lot going on. That's a good
> thing, right? :-)]
> >>
> >> Agenda with some info -
> >>
> >> * CLE 2.9.0 update - discussion about whether we can release as is,
> with some known issues, or if we need to delay to fix some important stuff
> (listed below). I'm leaning towards getting the 2.9.0 release out with the
> main benefit being the release of energy and focus for 2.9.1 and 2.10 (with
> a preference for defining 2.9.1 before starting the 2.10 discussion). CLE
> release team will have final weigh in on Thursday.
> >>
> >> * 2.9.1 tied up with 2.9.0. Let's focus mostly on 2.9.0 go / no go ?
> >>
> >> * Mobile update
> >> - Steering committee members :
> >> * Christian Bond, Leaning Forward Technology, LLC
> >> * Matthew Buckett, Oxford University, UK
> >> * Jon Crutchfield, University of Notre Dame
> >> * Ian Dolphin, member ex officio, Sakai Board and
> Foundation.
> >> * Kim Eke, University of North Carolina, Chapel Hill
> >> * Doug Johnson, University of Florida, Project Manager
> >> - Name of Mobile effort:
> >> * “Keitai” – Japanese for “cell” as in “cell phone.”
> >> - Purpose of Mobile effort:
> >> To improve the capabilities of the Entity Broker in Sakai
> CLE 2.10+ to enhance communication with mobile devices; and to upgrade
> existing core tools and selected Contrib tools to take advantage of
> improved Entity Broker capabilities leading to a mobile-enabled Sakai CLE.
> It should be noted that the purpose of this project is to “mobile enable”
> Sakai, not to create mobile apps themselves. This leaves to each Sakai
> institution the choice of developing their own apps or hiring third-party
> companies to do this development as well as the choice of which Sakai
> functions each institution wishes to enable and support in the mobile
> environment.
> >> - Affects the following versions of CLE:
> >> * code is targeted for version 2.10 with back porting to
> 2.9
> >>
> >> * Outline of Presentation for Educause:
> >> * Shared slide set with Ian Dolphin and Chuck Severance
> >> * Will "borrow" some from TCC Atlanta slide set (thanks TCC!)
> >> * Will keep number of slides down to a maximum of about 15,
> plus or minus. Won't necessarily need to use all slides in all
> presentations. We will cover Apereo, Sakai CLE 2.9 awesomeness, current
> 2.10 view (with caveat that still in planning stage and could change
> significantly), one or two slides on OAE, simply what is being done from
> this point forward, where it is headed. Base OAE on Nico's recent email.
> Target audience will be folks new to Sakai, but will also have specifics
> for folks who have/are familiar with Sakai and wish to know what's new.
> Part of Sakai's awesomeness should include the Sakai community and
> Community source model, standards base, scaleability, expandability,
> internationalization, accessibility, LTI, etc.
> >>
> >> *******************************************
> >> * 2.9.0 Summary *
> >> *******************************************
> >>
> >> Help documentation updates not making it in … plus …
> >>
> >> A la' Matt Jones:
> >>
> >> <begin MJ>
> >> At the moment we've got-
> >>
> >> - KNL-725 - Probably won't want to convert this column for Oracle, I'd
> just change the timestamp in the conversion script and advise Oracle users
> to either restart after every daylight time switch or set the property
> >> expired at org.sakaiproject.cluster.api.ClusterService=4200
> >> So that clusters won't expire for 1 hour 10 minutes (default 10
> minutes). This will catch the daylight expiration in either case. I don't
> currently have Oracle so can't test this out, and was hoping IU or Michigan
> would commit this change or advise further.
> >>
> >> - SAK-22801 - Normally wouldn't be a problem as the node has to crash
> while triggers are being fired. There is a database cleanup workaround, and
> it might not even affect Oracle or all versions of Mysql. There might be a
> property fix that can be added to a 2.9.x release as well, but just useful
> to know about if your system isn't starting up. (Though I've not seen this
> one yet, so seems unlikely)
> >>
> >> I'm sure there's other stuff that needs to be better documented like
> optimized cache properties, not to mention all of the other 2.9 properties.
> But nothing that's super serious.
> >>
> >> In either case, I'll still go through with releasing rc03 (hopefully
> today). Should the tcc have a vote this week on a "go-no-go" on 2.9.0 and
> waiting until all documentation is done? Or just putting the "Seth
> disclaimer" 2.9.0 release. :)
> >> </end MJ>
> >>
> >>
> >> On Oct 29, 2012, at 3:08 PM, Neal Caidin <
> nealcaidin at sakaifoundation.org> wrote:
> >>
> >>>
> >>> Any agenda items folks?
> >>>
> >>> Proposed Agenda
> >>> --------------------------
> >>> * CLE 2.9.0 update
> >>> * CLE 2.9.1
> >>> * Mobile update
> >>> * Outline of my presentation for Educause
> >>>
> >>>
> >>> I hope to have at least a rough sketch of my Educause thoughts I can
> send out Tuesday, in advance of the meeting. I should also be able to
> either forward stuff from Doug Johnson, U of Florida, on mobile, or
> summarize. I'm sending daily updates on 2.9.0 release, which is very tight
> to get out this week/ early next week. The main thing about 2.9.1 is that
> we should start planning this as soon as 2.9.0 is out the door. Let's
> define scope and a target date. One thing we will need to get into 2.9.1
> are updated help files. Unfortunately there was a SNAFU and updated help
> files are not getting into 2.9.0, just not enough time and we don't want to
> hold up the release anymore.
> >>>
> >>> Regards,
> >>>
> >>> Neal Caidin
> >>>
> >>> Sakai CLE Community Coordinator
> >>> nealcaidin at sakaifoundation.org
> >>> Skype: nealkdin
> >>> AIM: ncaidin at aol.com
> >>>
> >>>
> >>>
> >>>
> >>
> >
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20121031/190b9dd0/attachment.html
More information about the sakai2-tcc
mailing list