The 0.14.0 release blog-post

[kain88-de]

Lets start the next blog post text early. I think it can also serve as an announcement mail for the next release, or we just link to the blog post.

If you think you made a big change to the library and want to explain it in more detail this is the right place.

[richardjgowers]

So this is a quasi WIP branch that we merge on release?

[kain88-de]

Yes that's what I thought.

[orbeckst]

Please double check and then someone else can make it go live.

(Do you want to keep this PR around and then merge & reopen?)

[orbeckst]

@richardjgowers can you announce to the list once everything is life?

@philipwfowler can then handle the "social" aspects, i,e,, tweet etc.

[kain88-de]

I changed the wording a little bit. Otherwise it reads nice to me and it shows of the new features very nicely.

[orbeckst]

As far as I'm concerned it's good to go.

Oliver Beckstein
email: orbeckst@gmail.com

Am Feb 28, 2016 um 13:45 schrieb kain88-de notifications@github.com:

I changed the wording a little bit. Otherwise it reads nice to me and it shows of the new features very nicely.

—
Reply to this email directly or view it on GitHub.

[orbeckst]

Blog post live

[richardjgowers]

Mailing list done

[philipwfowler]

And tweeted. Will tweet again this pm for US time.

—Phil

On 29 Feb 2016, at 10:45, Richard Gowers notifications@github.com wrote:

Mailing list done

—
Reply to this email directly or view it on GitHub #8 (comment).

[orbeckst]

Thanks!

Now onwards an upwards (ie, towards getting MDAnalysis/mdanalysis#363 in).

Are we going to re-use the next-release branch for the next blog post?

Oliver Beckstein
email: orbeckst@gmail.com

Am Feb 29, 2016 um 2:45 schrieb Richard Gowers notifications@github.com:

Mailing list done

—
Reply to this email directly or view it on GitHub.

[kain88-de]

I regenerated the branch now. Could be that you need to force-update. Plain reusing and rebasing onto master would be better next time.