diaspora* software release

Agree, 0.5 out with warnings about alpha chat.

There are 9 issues in the milestone at the moment. I'd say lets cut an RC out from current develop and then only merge into the 0.5 RC fixes - no more features that introduce potential regression and delay 0.5.

@jhass @florianstaudacher @zauberstahl @steffenvanbergerem ? I'll volunteer to do the cutting and promoting the RC to podmins.

Dennis:

Nah. Either a 0.5.0.0 with or without a chat. A 0.4.9.9 would be invalid.

My vote is on releasing with opt-in'able chats and a fat warning it is very, very alpha.

Jason:

I’d say lets cut an RC out from current develop and then only merge into the 0.5 RC fixes - no more features that introduce potential regression and delay 0.5.

This sounds like a good plan to me.

So we should start writing the RC announcement. It will be posted by diaspora HQ, on diasporaforum.org and on the google groups. I'm not too sure about the blog.

The pad we usually use to prepare release annoucement is http://pad.spored.de/p/release_notes but there's actually a 502.

I think it's best to put only actual release announcements on the blog, rather than RC posts. We could do an interim 'the next version of Diaspora is coming soon' post for the blog, though, just to keep blog activity going and perhaps generate interest.

Yeah, the blog is probably not a good idea for RC.

If no one objects, I could create the release branch maybe tomorrow or in coming days Jonne had no objections on IRC.

looks good to me, maybe a last check on open PR to see if something can be merged? I would like to solve https://github.com/diaspora/diaspora/pull/5743 first for example.

And I'd like to solve https://github.com/diaspora/diaspora/pull/5480 too.

Thanks, Jason. This is exciting!

I agree that we should have a code freeze asap and fix / merge the 7 remaining issues / PRs in https://github.com/diaspora/diaspora/milestones/next-major.

Is anyone able to provide a likely ETA for those remaining issues?