> -----Original Message----- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Marc Sune > Sent: Tuesday, October 21, 2014 9:23 AM > To: <dev at dpdk.org> > Subject: [dpdk-dev] development/integration branch? > > Good morning, > > Some DPDK users, including myself, use a clone of the git repository to > compile DPDK for their applications, instead of downloading the tarball > of each release. > > In my opinion, it would be useful for such users that the master branch > contains only stable releases, to prevent (mistakenly) to use a wip DPDK > version, and jump quickly to the latest stable with a simple git pull > without having to check the tags. Also new users would clone the repo > and get only the stable release. > > So I would propose to use an integration/development branch, where the > patches are integrated and only push to master once a stable release is > tagged in this integration branch. > > Thoughts? > > best > marc
Ideally, our master branch should always be good and stable, but given reality often interferes with such good intentions I think that having dev branches is not a bad idea. However, what we may lose by doing so is having a larger group of people constantly using the master branch and reporting problems to us. On balance, I'd be slightly in favour of this suggestion. /Bruce
