[sakai2-tcc] Proposal: release Sakai 2.9.0 on Friday, November 9 barring any new blockers (Voting now open)

[Steve Swinsburg]

> 
> The release early, release often is more about getting bugs fixed, getting individual jiras verified, getting fixes merged into the 2.9.x branches and getting all of the changes documented. All of this effort aside from Neal is volunteered by the community and some weeks seem to have more time from the community than others. The release team will need to determine what criteria for making a 2.9.1 release. As of now, everything we expect to have in a release (that was verified and ready to merge) is in the release. I don't know of anything anyone is sitting on waiting in the wings to immediately merge for 2.9.1, but we'll find out.
> 

A while back we talked about releases being timed, ie every quarter, though that might introduce issues if we cant get testing resources. 

Totally agree that we need to draw the line somewhere, cut a release and move onwards so its out there and people. Otherwise we end up in the situation that was alluded to earlier, where people are running the maintenance branches instead of tags, because the tags are few and far between and they can get fixes faster in a branch. That means that actually making releases is a waste of time since no one uses them. That should be reversed so that people are confident to run tags and the community knows when they will be coming.



> Re this:
>> Also the actual release process (from branch management, to cutting releases) is almost entirely just Sam and myself which is far from ideal. In the past, Anthony helped out significantly with this, and ideally Neal would be able to assist, but it still feels like this *could* be a few months from happening. I'm planning on spending a day or two in North Carolina next week with Neal and Aaron to start on some of the more technical aspects of the release process. These were the 3-6 month goals the TCC initially set out in the CLECC onboarding.
> 
> 
> Could we discuss those on list before anything is implemented? I think we rushed though parts of the changes for 2.9 which ended up causing some problems early on. It could be streamlined, definitely.
> 
> Discuss what specifically?

Any technical aspects that might need to occur.

> I don't believe anything substantial would change for the 2.9 process but it would be useful to have someone else involved in merging and releasing indies.

I used to do a lot of this. Merging, easy. Releasing, I have absolutely no idea how to do that now. Is the guide still relevant/up to date? 

> I think there should be a lot of changes for 2.10 which would for sure be on list or at a venue with a large number of TCC members (some upcoming conference), but I don't believe that discussion would be started until at least January.

Cool.


cheers,
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20121107/4f9994f1/attachment.html