denemo-devel
[Top][All Lists]
Advanced

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

Re: [Denemo-devel] Release 1.1


From: Richard Shann
Subject: Re: [Denemo-devel] Release 1.1
Date: Sun, 24 Nov 2013 11:09:13 +0000

On Fri, 2013-11-22 at 23:56 +0100, Éloi Rivard wrote:
> A git tag points on one commit, no matter on which branch it is
> (master or anything else).
> 
> Branches to points to one commit, not a "set", but the difference is
> that when you append a new commit, the branch points to the newer
> commit.
> 
> When you consider a commit, you also consider its parents, that is
> what we feel we deal with "sets" of commits.
> 
> 
> Since you don't seem very cumfortable with tags: I can propose you
> another workflow:

I suggest we make things much simpler: when we want to make a release we
create a branch labelled stable-i.j.k as before, and when the
translations are in (and any fixes needed during testing) we create the
final candidate tarball. Once this is tested we upload to ftp.gnu.org
and announce the release. Then we delete the branch.

The reasoning is simple: we are not a library that needs to maintain
more than one version. We will never issue a release based on an old
release rather than based on master. And, this is a process we already
know how to do - we are severely short of resource for doing
infrastructure.

(Of course, we can transform the release branch into a tag if folk
prefer and someone knows how ...)

If this is acceptable could someone who knows how create the branch
stable-1.1.0 so that we can start testing.

Richard







reply via email to

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