Release announcements

I think the same message, although given that there are no previous release announcements on the blog, we could perhaps include a very short intro to release announcements explaining what it's all about, perhaps progress up to this point.

Same text is enough imho - but of course it can be longer if someone wants to be creative - the important thing IMHO is that it's posted at the same time as other communications.

If someone can give me some warning of when the release will be made, I'll be happy to post to DHQ and blog.

@flaburgan @goob @steffenvanbergerem @seantilleycommunit I wrote some thanks in the release announcement, going through commits and trying to figure out what each person did ;) Does the text sound good? Feel free to modify. Tagged you because you've commented here.
Anyone else who needs special mention?

@jonnehass @dennisschubert @florianstaudacher - https://github.com/diaspora/diaspora/pull/5008 and https://github.com/diaspora/diaspora/pull/5007 need merging - and I think then we're ready to go! I'm free to do some release stuff later in the evening today, say approx 6-8pm UTC.

Wouldn't we need some time to make sure these fixes don't have any unintended side-effects before releasing?

Thanks for that work tracking down contributors, @jaywink.
I've added links to people's profiles in Github.

I've also noticed that many links in the changelog are to the original issue reports rather than the pull requests, as I thought they are supposed to be. I'll push an updated changelog now.

@goob release coming now, if you want to follow it on IRC. :)

@jasonrobinson last changes are pulled in diaspora-fr, if you want to redo your tests on the bookmarklet there, just to check.

@goob well I think we've already had a code freeze for quite some time to find bugs. 5007 was to revert one such bug introduced in develop, 5008 to fix another regression. IMHO we are ready for release, unless no one has strong objections..

Planning to do that in an hour or two - so shout now if you want to! :)

@goob @flaburgan will one of you be around today later on IRC maybe? Would be nice to get the blog post posted around the same time that other communications is done. I've access to DHQ, but not the blog.

Yeah I'm available ;)

@jaywink if you post from DHQ I'll see it in my stream and post it to the blog then. Should be popping in every couple of hours so I'll pick it up then.

Release done, nice work everybody :)

Bang, 0.4.1.0 coming up - if no one opposes it will be pushed out tomorrow. Release announcement wip here: http://pad.spored.de/p/release_notes .. feel free to edit.

I'll be adding something about the ToS and Rake emailer to the changelog before the release and reading it through with someone before pushing the release out (sometime late evening on Sunday). I don't mind also doing the blog since I now have access there too :)

release notes approved ;)

Have just edited the release announcement with links to Github profiles of contributors, plus some minor tweaks to the text.

ToS changelog looks good, have made a couple of small suggestions.

@goob thanks for the profile links, totally forgot to add them. Will make your grammar change in the changelog pull, merge it and then push out the release.

So, yeah, it's out! Please share :D

https://blog.diasporafoundation.org/7-diaspora-version-0-4-1-0-released

Thank you Jason!

Just blogged the 0.5.6.0 release announcement and have updated the pad.

Thanks @goob!

So the good news of the week-end is the merge by Dennis and Jonne of the new federation gem by Benjamin. It's the most important change done by the community so far.

There are still issues to solve before the release but I feel like we can start to prepare its promotion, because there is work to do ;)

On our blog:
We could write a separate blogpost only about the new migration. I was also thinking about the OpenID connect, not sure how big we want to promote that.

In diaspora*:
We could promote 0.6 as we did for 0.1. To do that, we basically need to:
- Choose which features we want to promote
- Create an image for 0.6
- Pick an hashtag for 0.6 (#diaspora0600 for example)
- Write the posts
- Would be even better if we can translate them

In the press:

• Write a press release
• Translate it
• For each language we have a translation,
  • List the press websites which could be interested
  • Send them the press release

Any other idea?

We could write a separate blogpost only about the new migration.

I thought about that yesterday, and tried to get started, but (a) I don't understand enough about what the changes are (apart from the fact that they are AMAZING), and (b) I'm not well enough at the moment to do it. But I would like to help if I can. If one of you wants to write something I'll be happy to edit it and put it on the blog. Same for in diaspora and press release. Just let me know if I can help.

I reckon the image for 0.6 could somehow suggest really effective federation/communication.

Hi, is there a specific font chosen for com ?
What about this image as backgroud (can not find where it come from, was posted on diaspora here : https://diaspora-fr.org/posts/1714909)

The 'official' typefaces for branding are either Roboto (a free font) or Helvetica. See this wiki article.

You'd need to establish the copyright/licence status of any image before using it.

Thanks goob. Roboto is fine. As for the licence I have no idea, tried with google reverse image search but no luck. I asked on the post above.

Just wondering : is the version number not too techy or geeky with four digits 0.6.0.0 or 0600 for non technically interested people ? 0.6 or 06 would be sufficient and why not finding names (like Mac does but also Debian or Linux Mint…) ?

The 27th of August will be the birthday of diaspora* as a community run project. It was 4 years ago! It would be nice to synchronize the release of the new major version and the birthday. The traditionnal release pad is currently down. I opened a new one dedicated to the 0.6.0.0 release to wrote diaspora, blog and press message.

Great idea… 4 years ! I can't believe it ! Time's go so fast…

Would it be possible to release 0.6 for the 27th ?

6107 is the last big blocker for the release. Do we want to officially target the 27th of August and so set it as the milestone date on github? We could start to tease officially if the date is fixed.

Okay. If and only if #6107 is officially merged <= this Friday, I'll freeze 0.6.0.0 on this Sunday. I guess we can deal with one week of freezing, so the release would be the 28th (not the 27th, we release on Sunday).

Sounds good?

Oh, and 6989, which is a regression that popped up today. :)

It would be fantastic to release on the anniversary, but is it worth the risk of halving the freeze time? I totally trust the core members to make that decision, but I'd back the view that it's only worth going for the release on the anniversary if there isn't an increased risk of problems after release, especially as this is by far our biggest release so far.

If @denschub and others in the core feel that a one-week is acceptable, would it be worth now publicising via the HQ account to ask as many people as possible to test it, and test it hard and fast, once it's frozen? That way hopefully any issues would be caught in the week before release.

If I can help with publicising, please let me know.

@goob There are a lot of pods that already run on the develop branch (https://the-federation.info/, version 0.5.99.0 are develop branch pods) including Geraspora, TheRealTalk.org, Sechat* and diaspora-fr. Those 4 pods had more than 5000 active users in the last month so I feel quite confident about the freeze of one week.

OK, great. Let's do this thing!