git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: life cycle documentation

From
BHBen Harper <ben.harper@rackspace.com>
Date
Oct 27, 2014, 14:52 UTC
Message-ID
<544E5C2F.3090800@rackspace.com>
In-Reply-To
<20141024215607.GH312818@vauxhall.crustytoothpaste.net>
On 10/24/2014 04:56 PM, brian m. carlson wrote:
Show 18 quoted lines
> 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

Previous: brian m. carlsonNext: brian m. carlson
Message 3 of 4 in “life cycle documentation”
  1. Ben HarperOct 23, 2014
  2. brian m. carlsonOct 24, 2014
  3. Ben HarperOct 27, 2014
  4. brian m. carlsonOct 27, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.