On Tue, Mar 5, 2019 at 8:25 PM David C. Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> wrote: > > On 03/05/2019 05:39 PM, Joel Klinghed wrote: > > Well, the changelog (https://www.imagemagick.org/script/changelog.php) > > is fairly clear about the upstream release cycle: > > > > 2019-03-05 7.0.8-32 > > 2019-03-04 7.0.8-31 > > 2019-03-03 7.0.8-30 > > 2019-02-28 7.0.8-29 > > Yes, that seems to be more a side-effect of the ease of creating a release on > git rather than the historical deliberative process of what to include, patch > and the normal Q&A that takes place during the 'alpha', 'beta' stages before > we reach a 'release'. > > The changelog seems to reflect that Arch is NOT following the stable branch of > imagemagick. > > The latest release on the "Master" branch is: > > Release build (7.0.8-27) (released 24 days ago) > https://github.com/ImageMagick/ImageMagick/releases/tag/7.0.8-27 > > Why are we not tracking Master? I don't think this is accurate. Why do you say this? Where are you seeing that -28+ isn't considered stable? I'm taking all of this to mean ImageMagick just hasn't remembered to tag release numbers on github since -27. The ChangeLog doesn't indicate 28+ isn't stable, and looking at their past github tags, it's not looking to me like they have a stable/unstable concept. The ChangeLog indicates -32 is git commit 58d9c4692, which is on the github master branch, currently 4 back from HEAD.
