Skip to content

Repo versions, tags, releases and branches #46

Closed

Description

@mitsukarenai

Hi there, AUR packager for "darkcoin" reporting in 😉
As of today, I update the AUR package for every 0.10.15.x release, as soon as I see them. This means by that time I check my RSS feeds, a few version numbers get skipped (was v0.10.15.3 just before, now I pushed v0.10.15.6). Sadly, Github is mixing tags and releases for enforcement and master branches, so filtering out by branch isn't quite easy. And all tags get a release.

The website isn't very helpful, as it's lagging on the master releases (shows v10.14.1 on a post 2 days ago, when v10.14.2 has been tagged+released 4 days ago).

What do you recommend for the time being ? Following every enforcement release on Github or rather sticking to master-only releases as announced on the website ?

Activity

  1. vertoe commented on Oct 29, 2014

    @vertoe

    I'm maintaining the darkcoin-git AUR package and I keep the PKGBUILD usually aligned for the bleeding-edge users, sometimes switching branches.

    As the darkcoin main package should be for regular users, you should stick to tags of the master branch only if possible.

  2. added 3 commits that reference this issue on Jul 6, 2020
  3. added a commit that references this issue on Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions