On Wed, 8 Jan 2014 03:41:37 +0100 (CET)
[email protected] wrote:
> > On Tue, 07 Jan 2014 23:33:52 +0000
> > Brian Drummond <[email protected]> wrote:
> > > On Tue, 2014-01-07 at 06:38 +0100, [email protected] wrote:
> > > > > I have also added the tag 0.31rc1 (Tristan, should I just
> > > > > re-tag
> > > > > as 0.31?)
> > > >
> > > > (I would have created a branch-0.31, and tag there)
> > >
> > > There are now two branches; ghdl-0.31 and default.
> > >
> >
> > I'm not sure whether or not it might seem excessively pedantic for a
> > small project, but some [explicit] conventions within the
> > development,
> > documentation, and release engineering processes could make it
> > easier to maintain a consistent/coherent system.
>
> I agree. There were some doc in diet.sh, but it's somewhat outdated.
>
This might be insanely over-elaborate but just to get a brainstorming
session started, how about this scenario:
* -current is where active development work is done.
* -release is a frozen point in the history of the source tree.
* -maintenance is where critical bug fixes to a -release are made.
,--------o-------X 0.31Maintenance
| .
| . ,-----o----> 0.32Maintenance
| . | .
| . | .
-->0.31Release----->0.32Release----> 0.33Current
Time --->
* -stable is a periodic snapshot of -current; made when -current
stabilizes enough to build cleanly and pass basic testing.
-->0.33Stable1----->0.33Stable2----> 0.33Current
* -RC : when -stable is internally consistent, rigorous testing and
polishing can begin on a Release Candidate snapshot.
-->0.33Stable[N]-->0.33RC1-->0.33RC2-->0.33RC[N]
* -release : when everyone is happy with a Release Candidate.
-->0.33RC[N]-->0.33Release
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
