From: "Wiles, Keith" <keith.wiles@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] GIT workflow model to help solve some of the problems
Date: Thu, 22 Oct 2015 13:13:57 +0000 [thread overview]
Message-ID: <8EE6789A-1AFE-470F-BE3F-F39E37A12577@intel.com> (raw)
I have been looking at the a GIT flow model that seems to help with our backlog problem and how we stage releases.
I found this model a few years ago and find it to be very reasonable and helps us with development.
http://nvie.com/posts/a-successful-git-branching-model/
The model may not be perfect, but it does give us the next branch via the develop branch and gets any bugs/patches off the master branch. I have not found a simpler solution that does not have problem and this one may have problems as well, but it seem to be reasonable. Some call the develop branch the ‘next’ branch, but it does not matter what it is called IMO.
—
Regards,
++Keith Wiles
Intel Corporation
next reply other threads:[~2015-10-22 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 13:13 Wiles, Keith [this message]
2015-10-22 13:56 ` Richardson, Bruce
2015-10-22 14:03 ` Wiles, Keith
2015-10-22 15:56 ` Stephen Hemminger
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=8EE6789A-1AFE-470F-BE3F-F39E37A12577@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
/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).