I'm not one for RC candidates unless needed for some reason.
Since we aim to release straight from the git master baseline (with just the version bump update), there are no merging various branching issues (i.e. this has already been done). I suppose the best practise is to announce our release intentions, which have happened in the past with I remember at least one 'string freeze' message. Previously I don't think between perhaps myself, Guilhem and (too a lesser extent) Greg, any one has shown an explicit interest in releases since we declared version 1.0, although various Distro's have picked up releases seemlessly - thank you. Some disto's offer 'continuous integration' anyway - I always hope that any individual git version (or at least after a merge stage) should be OK for release. Thus as far as I'm concerned posting some messages to this mailing list about the release intention is good enough. NB I had already responded to Greg, and (I believe) he's happy with the git release method Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. ________________________________ > Date: Wed, 6 Feb 2013 22:23:11 +0100 > Subject: Re: [Viking-devel] Imminent Viking 1.4 Release > From: guilhem.bonnefi...@gmail.com > To: g...@ir.bbn.com > CC: rw_nor...@hotmail.com; viking-devel@lists.sourceforge.net > > Hi Greg, > > I think this is a recurrent question, each time a significant release > is approaching. Deciding if a software like viking needs or not a > release candidate cycle is an infinite debate. Last time, we discuss > this topic, we decided to avoid release candidates. Instead, we release > the version when it is ready and fix bugs in a following release. Last > example is version 1.3.2.1. > > If you want to prepare a little, I think you can already fetch the > current Git master branch. If you really prefer a pre-packaged tarball, > I can send you the current version. But, as far as I know, a > significant release related job is not job: writing the 1.4 part of > file NEWS. > But, perhaps Robert has another point of view. > > 2013/2/5 Greg Troxel <g...@ir.bbn.com<mailto:g...@ir.bbn.com>> > > When it's almost ready, can you make a candidate release tarball, using > the same mechanism as you will use for the release, and put it up as > viking-1.4rc0.tar.gz? That way I can test the packaging path, and > others can too, and we can fix anything small. > > > ------------------------------------------------------------------------------ > > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Viking-devel mailing list > Viking-devel@lists.sourceforge.net<mailto:Viking-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/viking-devel > Viking home page: http://viking.sf.net/ > > > > -- > Guilhem BONNEFILLE > -=- JID: gu...@im.apinc.org<mailto:gu...@im.apinc.org> MSN: > guilhem_bonnefi...@hotmail.com<mailto:guilhem_bonnefi...@hotmail.com> > -=- mailto:guilhem.bonnefi...@gmail.com<mailto:guilhem.bonnefi...@gmail.com> > -=- http://nathguil.free.fr/ ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
