Release 0.11.0

[SeanTAllen]

It's close to that time again.

It is:

• about the be the first of the month
• we've gone more than 30 days without a release

Looking at the changes, 0.11.0 seems to be the appropriate version.

Anyone have time to do this in the next few days?

[Praetonus]

Since #1521 temporarily removed support of GCC 4.7 and 4.8, we might want to delay that release until support is restored. I'm working on implementing the algorithm discussed in #1521, it should be ready in the next few days.

[SeanTAllen]

@Praetonus sounds good to me.

[SeanTAllen]

@Praetonus @jemc We ready to do this release?

[Praetonus]

@SeanTAllen Apparently #1610 broke the build for Clang 3.5. It should be trivial to fix, can we hold off the release until that's resolved?

[SeanTAllen]

Yup.

[SeanTAllen]

@Praetonus has the clang 3.5 issue been resolved?

[jemc]

@SeanTAllen yes.

[SeanTAllen]

Ok, so @jemc @Praetonus shall i do a release this weekend?

[jemc]

No objections from me.

[SeanTAllen]

I'm going to assume that 1 ok is enough. TravisCI and Appveyor are all good. Going to start the release.

[SeanTAllen]

@Theodus i'm going to assume the release script wasn't tested on OSX? because it errors out on me...

sed: 1: "CHANGELOG.md": invalid command code C

and when I use -E to get GNU sed compat I get:

sed: 1: "/## \[unreleased\] \- u ...": command c expects \ followed by text

[SeanTAllen]

@Theodus it appears the sed usage is non portable:

http://stackoverflow.com/questions/4247068/sed-command-with-i-option-failing-on-mac-but-works-on-linux

[SeanTAllen]

@Theodus I pushed a fix for this. Its not pretty but...

4ccafba

Something we need to be aware of going forward.

Related: the differences between GNU and BSD said are awful. Ugh.

[SeanTAllen]

UPDATE: apparently that didnt work, i still end up with an error, working on it.

The Sed commands are all completely non portable and require GNU sed.

[SeanTAllen]

@Theodus i addressed by making GNU sed required. Kind of a pain but it works and I don't know sed and couldn't make the script portable otherwise:

21d37aa

[SeanTAllen]

Release is underway

[SeanTAllen]

release branch recreated. VERSION and CHANGELOG updated on master.

[SeanTAllen]

homebrew PR opened:

Homebrew/homebrew-core#10899

[SeanTAllen]

@stefantalpalaru release is underway.

[SeanTAllen]

The only update standard library docs on release task successfully executed. First time since the change, just wanted to note that all is in fact, good on that front.

[SeanTAllen]

Windows, RPM and Debian versions are available in Bintray.

Waiting on Homebrew.

Does anyone know why the Windows version creates two archives whereas RPM and Deb create one?

@killerswan ? ^^

[SeanTAllen]

Homebrew is done (damn that was fast).

The release process change over there, so I might need to update release docs a little.

I'll send out release notice email etc after I make myself some food.

[SeanTAllen]

Release notice sent. Only thing outstanding is Gentoo update that @stefantalpalaru maintains. I assume he still is and will leave this open for now.

[stefantalpalaru]

Gentoo ebuild updated. I'll make a PR with the fix for linking with "--as-needed".

[SeanTAllen]

Awesome. Thanks @stefantalpalaru.

[SeanTAllen]

re: duplicate windows entries, it appears that setting the tag causes a second appveyor build...