Current stable Granite tarball contains unstable code

[Maxime Gauduin]

Trying to build noise 0.3.1 against granite 0.3.0 fails because some changes that happened post release in granite are needed. I can't push a bzr version of granite in the Arch Linux repositories, because of that, I'm unable to bump noise to 0.3.1.

Here's the full buildlog: https://paste.xinu.at/vFvL/

[Victor Martinez (victored)]

The 0.3.0 tarball on Granite's overview page was published on 2014-05-25 and there have been too many changes since then to roll back to that version.

Granite's 0.3 series is considered stable: https://code.launchpad.net/~elementary-pantheon/granite/0.3

Here you can download the tarball for the actual last stable revision of Granite 0.3: http://bazaar.launchpad.net/~elementary-pantheon/granite/0.3/tarball/850

[Maxime Gauduin (alucryd)]

Hi Victor,

Thanks for the quick answer!

I understand you can't roll back to 0.3.0 and I wouldn't want that anyway, but I'm afraid "considered stable" will not cut it. We are pretty serious about only pushing stable releases. Also, the build process has to be reproducible, but that tarball is generated on demand and its hash changes every time.

I would have thought that granite would get a 0.3.1 release when everything else did. Did something get in the way of a release, have you got any idea when the next granite release could occur?

Worst case scenario, if there is no imminent granite release, I will bzr pull the stable branch to justify skipping the hash verification, but that will be frowned upon :/

[Cody Garver (codygarver)]

Backstory: We used to release beta versions of software as stable, or at least public, releases. Granite's 0.3.0 tarball was one of these beta releases and was never updated after 0.3.0 actually became the stable version, several revisions later.

This will be rectified by releasing granite 0.3.1 soon.

[Anatol Pomozov (anatol)]

It would be great to see a new stable release of granite. Thank you.