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

Re: Reference for git.git release process

From
RGRaman Gupta <rocketraman@fastmail.fm>
Date
Mar 26, 2009, 14:29 UTC
Message-ID
<49CB9159.6030606@fastmail.fm>
In-Reply-To
<49CB3766.5090109@op5.se>
Andreas Ericsson wrote:
Show 14 quoted lines
> Junio C Hamano wrote:
>>
>> In addition, you can keep older maintenance track around, i.e.
>>
>>     git branch maint-X.Y.(Z-1) maint
>>         git checkout maint
>>         git merge master
>>
>> so that maintenance releases for even older codebase _could_ be issued
>> _if_ necessary.
>>
> 
> Assuming one tags ones releases (which one should, and git.git does),
> creating maint-X.Y.Z when it's actually needed is a far better approach.

This is only correct if the current tip of the maint branch is in fact the last tagged release i.e. that there is nothing pending on the maint branch that is intended for a maintenance release on the older codebase.

Cheers, Raman

Previous: Andreas Ericsson
Message 14 of 14 in “Reference for git.git release process”
  1. Raman GuptaMar 25, 2009
  2. Junio C HamanoMar 25, 2009
  3. Raman GuptaMar 25, 2009
  4. Junio C HamanoMar 25, 2009
  5. Junio C HamanoMar 26, 2009
  6. Jeff KingMar 26, 2009
  7. Junio C HamanoMar 26, 2009
  8. Jeff KingMar 26, 2009
  9. Junio C HamanoMar 26, 2009
  10. Jeff KingMar 26, 2009
  11. Junio C HamanoMar 26, 2009
  12. Shawn O. PearceMar 26, 2009
  13. Andreas EricssonMar 26, 2009
  14. Raman GuptaMar 26, 2009

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.