From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/howto: tracking git.git
Date: Sun, 16 May 2021 09:57:38 +0900 [thread overview]
Message-ID: <xmqqsg2n7awt.fsf@gitster.g> (raw)
In-Reply-To: <cbbde4f4-3e10-2c08-6ca1-6f22f8497194@gmail.com> (Bagas Sanjaya's message of "Sat, 15 May 2021 10:32:27 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> On 14/05/21 20.49, Junio C Hamano 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?
>>
>
> I think "maint" is maintenance branch for latest feature release.
> For feature stabilization it happens on "main", so "master" is fully
> polished.
With the status of being back-then-most polished plus only fixes and
no unnecessary new features that can introduce unstability yet to be
discovered, by definition 'maint' ought to be "more stable" than
'master', no?
In any case, as Đoàn Trần Công Danh pointed out, I think we have
most of these written down elsewhere, and it is easier for readers
if we can find a way to reorganize them and incorporate new stuff
that is brought in by this proposal.
prev parent reply other threads:[~2021-05-16 1:02 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
2021-05-15 3:32 ` Bagas Sanjaya
2021-05-16 0:57 ` Junio C Hamano [this message]
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=xmqqsg2n7awt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@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).