hydra-users
[Top][All Lists]
Advanced

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

Re: bison-master


From: Akim Demaille
Subject: Re: bison-master
Date: Tue, 21 Feb 2012 16:03:14 +0100

Le 21 févr. 2012 à 14:47, Rob Vermaas a écrit :

> Hi Akim,

Hi!

> We are currently only building the master branch for bison. If it is 
> desirable, we could add a jobset for another branch. 

Well, in that case it might be nice to have
two other Bison branches to be checked.  One
would be "maint" for the maintenance branch
(currently it is named branch-2.5, but it will
be renamed), and another would be "next", so
that we can run the test-suite before installing
changes in master.

Would that be good for you?  Currently neither
maint nor next exist, but if my fellow maintainers
agree, I think that's the best course, and we'll
create them.

BTW, might be there is already a standard followed
by other Hydrated projects for the same purpose?  I proposed
"next", but maybe "pu" is more appropriate?
These names come from suggestions in man gitworkflows.


Cheers!

   Graduation
       As a given feature goes from experimental to stable, it also
       "graduates" between the corresponding branches of the software. git.git
       uses the following integration branches:

       o    maint tracks the commits that should go into the next "maintenance
           release", i.e., update of the last released stable version;

       o    master tracks the commits that should go into the next release;

       o    next is intended as a testing branch for topics being tested for
           stability for master.

       There is a fourth official branch that is used slightly differently:

       o    pu (proposed updates) is an integration branch for things that are
           not quite ready for inclusion yet (see "Integration Branches"
           below).

       Each of the four branches is usually a direct descendant of the one
       above it.

       Conceptually, the feature enters at an unstable branch (usually next or
       pu), and "graduates" to master for the next release once it is
       considered stable enough.




reply via email to

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