Great! ----- Mail original ----- > On Tue, 2014-01-07 at 06:38 +0100, [email protected] wrote: > > > On Mon, 2014-01-06 at 22:21 +0100, Joris van Rantwijk wrote: > > > > On 2014-01-05, [email protected] wrote: > > > > > I think we are ready for a new release. > ... > > > > I'm looking forward to the release. Clearly a lot of bugs have > > > > been > > > > fixed and GHDL will be easier to build on modern systems. > > > > > > I have also added the tag 0.31rc1 (Tristan, should I just re-tag > > > as > > > 0.31?) > > > > It's up to you if you take the lead! > > > > (I would have created a branch-0.31, and tag there) > > At last I think I have it... > > There are now two branches; ghdl-0.31 and default. > > After cloning the repo (hg clone) or pulling changes to an existing > one, > hg update ghdl-0.31 > will select the stable 0.31 branch, which can be built or packaged > for > release. > > hg update default > should select the most current version; future changes should > normally > be to "default" unless they are critical and must be "backported" to > 0.31. > > See > http://hgbook.red-bean.com/read/managing-releases-and-branchy-development.html > for some information on working with branches. > > I backported the copyright dates, as an exercise. Then I made a > commit > to the "default" branch to keep "tip" attached to default, reducing > the > chance that a commit will happen to 0.31 by mistake... > > Hope it looks OK as an 0.31 release... > I'll make a source download package tomorrow if I can. > > - Brian > >
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
