[arch-general] Any particular reason for daily imagemagick updates?
All, More an observation than a problem, but is there any security reason for the flood of imagemagick updates, or are we basically getting nightlies every time a commit is pushed? Example: 5 hours Update to 7.0.8.32 arojas 27 hours Update to 7.0.8.31 arojas 2 days Update to 7.0.8.30 arojas 5 days Update to 7.0.8.29 arojas That's 4 in the past 5 days alone and two within 24 hours. It's small enough that updates are no issue, it just seems odd that the upstream release cycle is really that frequent. -- David C. Rankin, J.D.,P.E.
On Tue, 5 Mar 2019 17:30:24 -0600 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
All,
More an observation than a problem, but is there any security reason for the flood of imagemagick updates, or are we basically getting nightlies every time a commit is pushed? Example:
5 hours Update to 7.0.8.32 arojas 27 hours Update to 7.0.8.31 arojas 2 days Update to 7.0.8.30 arojas 5 days Update to 7.0.8.29 arojas
That's 4 in the past 5 days alone and two within 24 hours. It's small enough that updates are no issue, it just seems odd that the upstream release cycle is really that frequent.
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 /JK
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? -- David C. Rankin, J.D.,P.E.
On Tue, Mar 5, 2019 at 8:25 PM David C. Rankin <drankinatty@suddenlinkmail.com> 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.
On Tue, Mar 05, 2019 at 07:25:10PM -0600, David C. Rankin 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?
-- David C. Rankin, J.D.,P.E.
"The current release is ImageMagick 7.0.8-32." -- Felix M. Cobos
Am 06.03.19 um 02:25 schrieb David C. Rankin:
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?
That just shows that ImageMagick doesn't care about keeping a proper git repository with tagged releases. Have you recently read the git log? Not even the commit messages are useful. Most commits have just three dots as the commit message or if you are lucky a bug tracker id.
On 03/06/2019 03:43 AM, ProgAndy wrote:
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?
That just shows that ImageMagick doesn't care about keeping a proper git repository with tagged releases. Have you recently read the git log? Not even the commit messages are useful. Most commits have just three dots as the commit message or if you are lucky a bug tracker id.
That's my bad then. I went to gitub and just clicked "Releases". -- David C. Rankin, J.D.,P.E.
participants (5)
-
David C. Rankin
-
Felix M. Cobos
-
james harvey
-
Joel Klinghed
-
ProgAndy