From: Ernesto Maserati <ernesto.2.maserati@gmail.com>
To: git@vger.kernel.org
Subject: How to generate feature branch statistics?
Date: Wed, 20 Jul 2016 10:05:09 +0200 [thread overview]
Message-ID: <CAOHAwykGkfY7M30jT8t0k6Gsdy5QSBHmAPiWYoKibjUgS-G6hg@mail.gmail.com> (raw)
I assume that feature branches are not frequently enough merged into
master. Because of that we discover bugs later than we could with a more
continuous code integration. I don't want to discuss here whether feature
branches are good or bad.
I want just to ask is there a way how to generate a statistic for the
average duration of feature branches until they are merged to the master? I
would like to know if it is 1 day, 2 days or lets say 8 or 17 days. Also it
would be interesting to see the statistical outliers.
I hope my motivation became clear and what kind of git repository data I
would like to produce.
Any ideas?
next reply other threads:[~2016-07-20 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:05 Ernesto Maserati [this message]
2016-07-20 13:14 ` How to generate feature branch statistics? Jeff King
2016-07-20 18:49 ` Junio C Hamano
2016-07-20 23:10 ` Jakub Narębski
2016-07-20 23:31 ` Junio C Hamano
2016-07-20 13:56 ` Jakub Narębski
2016-07-20 18:10 ` Jakub Narębski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOHAwykGkfY7M30jT8t0k6Gsdy5QSBHmAPiWYoKibjUgS-G6hg@mail.gmail.com \
--to=ernesto.2.maserati@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).