unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: 2.0.x branched!
Date: Sat, 19 Feb 2011 00:17:54 +0100	[thread overview]
Message-ID: <m3ei750w65.fsf@unquote.localdomain> (raw)
In-Reply-To: <87aahtm63o.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 18 Feb 2011 20:37:47 +0000")

On Fri 18 Feb 2011 21:37, Neil Jerram <neil@ossau.uklinux.net> writes:

> Now that 2.0.0 is out, I presume the general procedure from now on
> should be:
>
> - committing safe 2.0.x stuff (in particular, as far as I'm concerned,
>   docs) to the stable-2.0 branch
>
> - committing anything else to master
>
> - periodically merging from stable-2.0 to master.
>
> Is that right?

That sounds about right to me, though I am quite ignorant in this
regard.  Compatible changes on 2.0.x seem fine to me; we should live in
2.0.x for a year or two I think.

Tough to plan for the future, though!

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-02-18 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 15:50 2.0.x branched! Ludovic Courtès
2011-02-18 20:37 ` Neil Jerram
2011-02-18 23:17   ` Andy Wingo [this message]
2011-02-18 23:25     ` Neil Jerram
2011-02-18 23:54     ` Mark H Weaver
2011-02-19 13:16       ` Andy Wingo
2011-02-19 18:25         ` Mark H Weaver
2011-02-20 11:02           ` Andy Wingo
2011-02-21 20:34     ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ei750w65.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).