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

Re: Status of kha/experimental

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Oct 9, 2007, 21:10 UTC
Message-ID
<b0943d9e0710091410w1559f1a0yb5055182fd289646@mail.gmail.com>
In-Reply-To
<20071007213307.GA32210@diana.vm.bytemark.co.uk>
On 07/10/2007, Karl Hasselström <kha@treskal.com> wrote:
Show 14 quoted lines
> On 2007-10-07 22:18:44 +0100, Catalin Marinas wrote:
>
> > How stable is the kha/experimental branch? Since there are more and
> > more bugs added to the tracking system, I'll have to start looking
> > at them before a 0.14 release. Is it worth merging the
> > kha/experimental now or we better wait for after 0.14?
>
> The idea is that experimental contains changes that need testing, but
> may not yet be ready for your master. (They are generally safe,
> though; I run StGit from my experimental branch at work, for example.)
> When I decide that they are ready, I move them to safe. If there are
> any patches you feel should be in safe rather than experimental, just
> ask. Or you could just take them directly from experimental without
> asking, of course. :-)

OK. My plan is to merge kha/safe and have a look at what seems safer to merge from kha/experimental. Fix bugs (and freeze the current features). Release 0.14. Merge kha/experimental entirely post 0.14 and test/stabilize it over couple of months. How does this sound?

-- 
Catalin
Previous: Karl HasselströmNext: Yann Dirson
Message 3 of 10 in “Status of kha/experimental”
  1. Catalin MarinasOct 7, 2007
  2. Karl HasselströmOct 7, 2007
  3. Catalin MarinasOct 9, 2007
  4. Yann DirsonOct 9, 2007
  5. Karl HasselströmOct 10, 2007
  6. Catalin MarinasOct 11, 2007
  7. Karl HasselströmOct 12, 2007
  8. Catalin MarinasOct 12, 2007
  9. David KågedalOct 10, 2007
  10. Karl HasselströmOct 10, 2007

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.