[Building Sakai] Proposal for Sakai release 10.0

[Anthony Whyte]

Recall that as regards lazy consensus proposals: silence equals consent.


On Fri, Jun 13, 2014 at 9:32 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> Right. Thanks for the clarification. That is my understanding, but I think
> I made a SNAFU on the language.
>
> I was cutting and pasting from the Decision register:
>
>
> https://confluence.sakaiproject.org/display/PMC/Proposal%3A+Switch+to+lazy+consensus+when+considering+community+release+proposals
>
> But I think I got confused by the voting at the botton, which I thought
> was a template to use for Lazy Consensus , but now I think it was the
> actual vote on the proposal to switch to lazy consensus so that voting is
> not necessary. LOL.
>
> Boy did I get myself confused!
>
> - Neal
>
>
>   Anthony Whyte <arwhyte at umich.edu>
>  June 13, 2014 at 9:27 AM
> Clarification regarding voting.  Lazy consensus proposals do *not*
> require a formal vote by PMC vote as is implied in the announcement above.
>  All that is required is 1) a summary statement describing that some action
> X is intended or will occur on Y date if no objection surfaces and 2) a
> sufficient time block for PMC members (or others) to raise substantive
> objections regarding the proposal.  If a PMC member raises a material
> objection, the proposal is blocked until a resolution can be found;
> objections raised by other members of the community will be taken under
> advisement.
>
> In certain cases, a PMC member may call for a formal roll call vote in an
> attempt to resolve an operational impasse but we should work hard to avoid
> such a situation as it tends to undercut our consensus-based decision
> model.
>
> cheers,
>
> Anthony
>
>
>
>
>
>   Neal Caidin <neal.caidin at apereo.org>
>  June 13, 2014 at 7:52 AM
> Hi sakai-dev and sakai-pmc,
>
> Proposal
> The Sakai Core team proposes to start the Sakai 10.0 release process by
> next Wednesday, June 18, assuming no new blockers are discovered.
>
> Background Information Overview
> We have released Sakai 10.0-RC02 (release candidate 02) on Wednesday
> afternoon, June 11, 2014. We have already fixed a few more bugs for RC03
> [1], and we have one issue which we hope to get fixed but is not a blocker.
> [2] and another issue which will be completed in conjunction with the
> release [3].
>
> Release notes are mostly done. Conversion scripts are completed. Property
> documentation is complete.
>
> Release of Artifacts - Matt and Earle
> Setup a new profile in the base pom i.e. "api".
> This profile will contain all modules that are api's and a few other
> modules who's artifacts need to be released (see master/pom.xml
> org.sakaiproject dependencies).
>
> Since the nexus pom contains the correct <distributionManagement/> and is
> inherited by all projects we would then use mavens deploy plugin all we
> will need to do is run maven deploy with the profile "api" activated. This
> will perform the deploy of just those modules in the "api" profile.
>
> This is our current best solution with least amount of changes though it
> may change depending on the outcome.
>
> Updating of Sakaiproject.org - Neal
> The following pages which reference the current Sakai release be updated
> by Neal following the release tag being cut, and before the official
> announcement
>
> http://www.sakaiproject.org/try-sakai
> http://www.sakaiproject.org/node/105
> http://www.sakaiproject.org/node/31
> http://www.sakaiproject.org
> http://sakaiproject.org/current-release
>
> Official release documentation - Matt and Neal
> http://source.sakaiproject.org/release currently points to
> http://source.sakaiproject.org/release/2.9.3 will instead point to
> http://source.sakaiproject.org/release/10.0 by updating
> www/release/index.html by adding the new url.
>
> Neal will update the documentation at
> http://source.sakaiproject.org/release/10.0 in advance of the release.
> Matt will validate at the time of release and before pointing
> http://source.sakaiproject.org/release to the new release docs.
>
> Release notes - Neal and Diego del Blanco Orbitg with input from Sakai
> Core Team, and Crowdsourcing encouraged (but not much input so far)
> Mostly completed and mostly translated into Spanish
> https://confluence.sakaiproject.org/pages/viewpage.action?pageId=86245732
>
> By rules of Lazy Consensus
> Voting on the question is now OPEN and will conclude no later than Monday,
> 16 June 2014, 23:59 UTC.
>
> Voting is restricted to the Sakai PMC, but input is requested and welcome
> from anyone in the community. This means you!
>
> As a reminder, this is a public, on-list vote with a "+1" signifying
> approval. Per PMC governance documents, a -1 vote must be accompanied by a
> detailed explanation. A single -1 vote based on a material objection will
> block action. However, -1 blocking votes can be overridden by a 2/3
> majority roll call vote of active PMC members.
>
>
> [1] Issues fixed for RC03 -
> https://jira.sakaiproject.org/issues/?jql=fixversion%20%3D%20%2210.0-rc03%22%20and%20resolution%20%3D%20'fixed
> <https://jira.sakaiproject.org/issues/?jql=fixversion%20%3D%20%2210.0-rc03%22%20and%20resolution%20%3D%20%27fixed>
> '
> [2] Critical issue hoping to fix for RC03, but not a blocker  (per Sakai
> core team call) - https://jira.sakaiproject.org/browse/SAK-25899
> [3] RSF version 0.8.0 for Sakai 10 -
> https://jira.sakaiproject.org/browse/SAK-25899
>
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140613/3f109bdb/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 992 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140613/3f109bdb/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140613/3f109bdb/attachment-0001.jpg