{"thread":{"id":"37792","subject":"life cycle documentation","startedAt":"2014-10-23T22:15:21Z","lastAt":"2014-10-27T23:02:09Z","messageCount":4,"participants":["Ben Harper","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"251001","messageId":"54497DF9.1050501@rackspace.com","threadId":"37792","inReplyTo":null,"subject":"life cycle documentation","fromName":"Ben Harper","fromEmail":"ben.harper@rackspace.com","sentAt":"2014-10-23T22:15:21Z","receivedAt":"2014-10-23T22:15:21Z","isPatch":false,"sender":{"key":"ben.harper@rackspace.com","avatar":null},"body":"Greetings,\n\nI am unable to find any documentation regarding the life cycle regarding \nthe various versions of git.  Is only the current version supported?  \nWhat about older minor/major versions?  At what point does a version go \nEOL? Currently, is only 2.1.2 supported?  I would entertain the thought \non creating a RELEASES document if the information is provided.\n\nBen Harper\nOS Deployment Services, RPMDEV\nRackspace Hosting & IUS Community\n"},{"id":"251029","messageId":"20141024215607.GH312818@vauxhall.crustytoothpaste.net","threadId":"37792","inReplyTo":"54497DF9.1050501@rackspace.com","subject":"Re: life cycle documentation","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2014-10-24T21:56:07Z","receivedAt":"2014-10-24T21:56:07Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Thu, Oct 23, 2014 at 05:15:21PM -0500, Ben Harper wrote:\n> Greetings,\n> \n> I am unable to find any documentation regarding the life cycle regarding the\n> various versions of git.  Is only the current version supported?  What about\n> older minor/major versions?  At what point does a version go EOL? Currently,\n> is only 2.1.2 supported?  I would entertain the thought on creating a\n> RELEASES document if the information is provided.\n\nThe development process is outlined at [0].  Usually there's just one\nsupported release (at the moment, 2.1.2), although I have occasionally\nseen releases out of order (from different branches).\n\nHaving said that, Git developers try very hard not to break things, so\nmany people are fine using an older version, such as the ones their\ndistros provide.  It is considered courteous to try the latest version\nbefore reporting a bug, however.\n\n[0] https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"},{"id":"251117","messageId":"544E5C2F.3090800@rackspace.com","threadId":"37792","inReplyTo":"20141024215607.GH312818@vauxhall.crustytoothpaste.net","subject":"Re: life cycle documentation","fromName":"Ben Harper","fromEmail":"ben.harper@rackspace.com","sentAt":"2014-10-27T14:52:31Z","receivedAt":"2014-10-27T14:52:31Z","isPatch":false,"sender":{"key":"ben.harper@rackspace.com","avatar":null},"body":"On 10/24/2014 04:56 PM, brian m. carlson wrote:\n> On Thu, Oct 23, 2014 at 05:15:21PM -0500, Ben Harper wrote:\n>> Greetings,\n>>\n>> I am unable to find any documentation regarding the life cycle regarding the\n>> various versions of git.  Is only the current version supported?  What about\n>> older minor/major versions?  At what point does a version go EOL? Currently,\n>> is only 2.1.2 supported?  I would entertain the thought on creating a\n>> RELEASES document if the information is provided.\n> The development process is outlined at [0].  Usually there's just one\n> supported release (at the moment, 2.1.2), although I have occasionally\n> seen releases out of order (from different branches).\n>\n> Having said that, Git developers try very hard not to break things, so\n> many people are fine using an older version, such as the ones their\n> distros provide.  It is considered courteous to try the latest version\n> before reporting a bug, however.\n>\n> [0] https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt\nHey Brian,\n\nThanks for the clarification.  Someone in IRC mentioned the \nmaintain-git.txt file.  I skimmed it and searched for some keywords, but \nwas unable to find the information I needed.\n\nDo you feel a RELEASES document is needed or is the maintain-git.txt \nfile sufficient?\n\nBen Harper\nOS Deployment Services, RPMDEV\nRackspace Hosting & IUS Community\n"},{"id":"251135","messageId":"20141027230209.GB422734@vauxhall.crustytoothpaste.net","threadId":"37792","inReplyTo":"544E5C2F.3090800@rackspace.com","subject":"Re: life cycle documentation","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2014-10-27T23:02:09Z","receivedAt":"2014-10-27T23:02:09Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Mon, Oct 27, 2014 at 09:52:31AM -0500, Ben Harper wrote:\n> Thanks for the clarification.  Someone in IRC mentioned the maintain-git.txt\n> file.  I skimmed it and searched for some keywords, but was unable to find\n> the information I needed.\n> \n> Do you feel a RELEASES document is needed or is the maintain-git.txt file\n> sufficient?\n\nI don't personally feel one is needed.  However, I'm a semi-regular on\nthe list, so my opinion of what would be helpful to people less familiar\nwith the project is going to be skewed.  If you were to send a patch to\nadd a releases.txt file in the Documentation directory, it would\nprobably be welcome.\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"}]}