From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Marc Sune <marc.sune@bisdn.de>, "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] development/integration branch?
Date: Tue, 21 Oct 2014 08:36:13 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0344210F9@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <544617E0.80502@bisdn.de>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marc Sune
> Sent: Tuesday, October 21, 2014 9:23 AM
> To: <dev@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
next prev parent reply other threads:[~2014-10-21 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:22 Marc Sune
2014-10-21 8:36 ` Richardson, Bruce [this message]
2014-10-21 8:46 ` Thomas Monjalon
2014-10-21 9:14 ` Marc Sune
2014-10-21 9:28 ` Thomas Monjalon
2014-10-21 9:38 ` Marc Sune
2014-10-21 13:50 ` Neil Horman
2014-10-22 7:00 ` Matthew Hall
2014-10-22 13:43 ` Stephen Hemminger
2014-10-22 15:54 ` Matthew Hall
2014-10-21 13:01 ` Stephen Hemminger
2014-10-23 9:19 ` Marc Sune
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59AF69C657FD0841A61C55336867B5B0344210F9@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=marc.sune@bisdn.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).