Supercollider: Keep tagging uniformity

Created on 20 Mar 2020  Â·  3Comments  Â·  Source: supercollider/supercollider

Hi! I package supercollider for Arch Linux. Currently I'm having troubles retrieving the current version from upstream (this repository), because 3.11-beta1 shadows the current latest stable (Version-3.11.0).

Tools, such as nvchecker are used by many downstreams (such as me) to track new versions of upstreams (such as supercollider). These tools - depending on configuration - rely on the tags of upstream repositories.

As 3.11-beta1 orders before Version-3.11.0 (according to semver), the tracking of versions is now stuck at 3.11-beta1 (and this tag has to be added to the list of ignored tags, which already contains 3.3 3.6-branch-point 3.4branchpoint)

A potential route out of this could be to switch to a tagging theme without the conventional prefix Version-, or deleting/replacing the 3.11-beta1 tag.

Looking at the output of git ls-remote -t https://github.com/supercollider/supercollider I also see many random tags, that should be subject to removal/renaming as they serve no versioning purpose or are not following the Version- convention.

Environment

  • SuperCollider version: n/a
  • Operating system: Arch Linux
  • Other details (Qt version, audio driver, etc.): n/a

Steps to reproduce

git ls-remote -t https://github.com/supercollider/supercollider

Expected vs. actual behavior

  • All tags are done with the conventional Version- prefix.
  • Tags without the conventional Version- shadow the ones with.
bug not a big issue organizational

Most helpful comment

I should have this done later today.
Josh

/*
Josh Parmenter
www.realizedsound.net/josh
*/

On Mar 20, 2020, at 04:31, Brian Heim notifications@github.com wrote:


i'm aware of this and have asked @joshpar to fix it at his convenience

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

All 3 comments

i'm aware of this and have asked @joshpar to fix it at his convenience

I should have this done later today.
Josh

/*
Josh Parmenter
www.realizedsound.net/josh
*/

On Mar 20, 2020, at 04:31, Brian Heim notifications@github.com wrote:


i'm aware of this and have asked @joshpar to fix it at his convenience

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

done now!

Was this page helpful?
0 / 5 - 0 ratings