Re: Release time

On Sat, Nov 24, 2018 at 5:19 PM Nick Morrott <[email protected]> wrote:

> I think a (significant) version bump is long overdue. Two questions:

I would add a third.  Should the project tag more regularly
so that release-monitoring.org picks up that there is a new
minor or patch level that should be eligible for re-packaging?
Note that some distros auto-generate a ticket about new
versions assigned to the package maintainers.  Certainly
not every commit deserves a tag, but only tagging once
a year means numerous updates are simply not being
re-packaged on a timely basis in some distros unless the
package maintainer performs some active checks, and
that is not always sustainable (automated push
notifications are going to be better).  I could easily imagine
a new tag (patch level) once every three to four months
if any (non-trivial?) commit has been performed, or even
more often for "significant" changes (I think I am one of
the guilty parties regarding recent significant changes).
Certainly semantic versions suggests that the patch
level is considered a common light-weight change.  I
suppose this could be handled by anyone who made a
commit open an issue requesting a tag, but than the
release manager has to have some guidance as to
how to decide to tag now.

btw, remember there was a discussion regarding both
renaming and/or disappearing older grabbers and
creating dummy files at the next release.  Perhaps time
to go back and see what needs to be done there
(maybe it was done, I don't know for sure, I just
remember the discussion that something needed to
be done for the next release, which is apparently now).