From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Documentation/howto: tracking git.git
Date: Fri, 14 May 2021 22:27:35 +0700 [thread overview]
Message-ID: <YJ6W50M+EJlIO1GJ@danh.dev> (raw)
In-Reply-To: <xmqqwns177cv.fsf@gitster.g>
On 2021-05-14 22:49:52+0900, Junio C Hamano <gitster@pobox.com> wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
> > +Available Branches
> > +------------------
> > +
> > +There are several branches on git.git with different purposes:
> > +
> > +master::
> > +This is the most stable branch. Changes (topics) that are merged
> > +to master should have been stabilized in next and suitable for
> > +production use. Feature releases (vX.Y.0) are cut from this
> > +branch.
>
> Isn't "maint" meant to be more stable?
>
> > +next::
> > +This is where topics that haven't been yet merged to master are
> > +stabilized and tested for breakage and regressions. It gives
> > +a summary forecast of what next batch of topics that will be
> > +merged to master looks like.
> > +
> > +seen::
> > +This is the most bleeding edge branch where all excited
> > +developments happened. All proposed topics are queued in seen
> > +by the maintainer. However, these may be buggy (have breakage or
> > +regressions). When topics queued are deemed good and ready for
> > +inclusion, they are graduated to next for stabilization.
>
> This is inconsistent with what has been written elsewhere about this
> integration branch. In short, you should not read anything more
> than "the maintainer happens to have seen these topics" out of the
> fact that a topic is in 'seen'. Not all proposed topics will be in
> this branch, and a branch that was in 'seen' on one day may not be
> there the next day, but that does not mean anything (certainly it
> does not mean the topic has been "rejected").
Well, I think most of this document's points has been written in
Documentation/howto/maintain-git.txt and
Documentation/SubmittingPatches.txt.
With only 2 above points, I think if we have this document in,
we'll have more things to maintain :shrug:
--
Danh
next prev parent reply other threads:[~2021-05-14 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 12:49 [PATCH] Documentation/howto: tracking git.git Bagas Sanjaya
2021-05-14 13:49 ` Junio C Hamano
2021-05-14 15:27 ` Đoàn Trần Công Danh [this message]
2021-05-15 3:32 ` Bagas Sanjaya
2021-05-16 0:57 ` Junio C Hamano
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=YJ6W50M+EJlIO1GJ@danh.dev \
--to=congdanhqx@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).