[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MIT-Scheme-devel] Missing tags for 10.x.y?

From: Taylor R Campbell
Subject: Re: [MIT-Scheme-devel] Missing tags for 10.x.y?
Date: Sun, 9 Dec 2018 01:40:32 +0000

> Date: Sat, 8 Dec 2018 17:18:21 -0800
> From: Chris Hanson <address@hidden>
> I'm not using tags, just the separate branch for the release.
> The tags don't seem to add much value, and I don't think that use is what
> they're meant for. And it's trivial to figure out what they would be from
> the release changelogs.

The tag provides name for a snapshot of exactly what the 10.1.3
release was if I want to reproduce it.  It is also helpful for, e.g.,
`git describe' to show what changes have happened since the latest
named release.  What other purpose are tags for, in any revision
control system?

> I am considering making a new branch for 10.2.x and so on, derived from
> release-10. I could be convinced that making a branch for every release
> would be reasonable.

In `a branch for every release', by `release' do you mean, e.g., `the
10.2.x series', or `the 10.2.1 release'?  A single branch for 10.2.x
from which we cut 10.2.0, 10.2.1, 10.2.2, &c., makes sense.  Separate
branches for 10.2.0, 10.2.1, 10.2.2, &c., don't seem to make much
sense to me -- presumably those are all fixed to a specific commit,
which is what tags are for.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]