From: Ben Harper <ben.harper@rackspace.com>
To: <git@vger.kernel.org>
Subject: Re: life cycle documentation
Date: Mon, 27 Oct 2014 09:52:31 -0500 [thread overview]
Message-ID: <544E5C2F.3090800@rackspace.com> (raw)
In-Reply-To: <20141024215607.GH312818@vauxhall.crustytoothpaste.net>
On 10/24/2014 04:56 PM, brian m. carlson wrote:
> On Thu, Oct 23, 2014 at 05:15:21PM -0500, Ben Harper wrote:
>> Greetings,
>>
>> I am unable to find any documentation regarding the life cycle regarding the
>> various versions of git. Is only the current version supported? What about
>> older minor/major versions? At what point does a version go EOL? Currently,
>> is only 2.1.2 supported? I would entertain the thought on creating a
>> RELEASES document if the information is provided.
> The development process is outlined at [0]. Usually there's just one
> supported release (at the moment, 2.1.2), although I have occasionally
> seen releases out of order (from different branches).
>
> Having said that, Git developers try very hard not to break things, so
> many people are fine using an older version, such as the ones their
> distros provide. It is considered courteous to try the latest version
> before reporting a bug, however.
>
> [0] https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt
Hey Brian,
Thanks for the clarification. Someone in IRC mentioned the
maintain-git.txt file. I skimmed it and searched for some keywords, but
was unable to find the information I needed.
Do you feel a RELEASES document is needed or is the maintain-git.txt
file sufficient?
Ben Harper
OS Deployment Services, RPMDEV
Rackspace Hosting & IUS Community
next prev parent reply other threads:[~2014-10-27 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 22:15 life cycle documentation Ben Harper
2014-10-24 21:56 ` brian m. carlson
2014-10-27 14:52 ` Ben Harper [this message]
2014-10-27 23:02 ` brian m. carlson
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=544E5C2F.3090800@rackspace.com \
--to=ben.harper@rackspace.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.
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).