Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: preparing the upcoming GDB 7.4 release
Date: Fri, 11 Nov 2011 02:34:00 -0000	[thread overview]
Message-ID: <20111111023407.GE5390@adacore.com> (raw)
In-Reply-To: <4EBC85E4.1080706@codesourcery.com>

> I thought we still have two weeks before branching, looks I am wrong.

No, we still have 2 weeks. What I am saying only applies if you think
you are not going to make it.

> Usually, how long it may take from receiving mail about "preparing the
> upcomming GDB X.X release" to branching? and how long from "branching"
> to release?

I try to give everyone a heads-up before we start the process. How
much before, well depends on my good will and how submerged by other
work I am... I don't have an alarm in my calendar that says "send
email to gdb-patches for XX weeks heads-up on next release branch",
but I do enter the tentative dates, and I try to send the email
when I think we're getting close.

There are several ways you can know about these dates:

  1. It's in the "schedule" page, part of the GDB website:
     http://www.sourceware.org/gdb/schedule/

  2. I make sure we discuss those dates at the end of each
     release cycle. Usually, not very many people are really
     interested in the next release date at that stage of the
     development. But the next cycle is announced.

So, although there is the heads-up that I send as a courtesy,
you should also be able to plan your work based on the dates
published several months in advance.

> I don't find anything useful to describe this release process.

What else do you want to know? I'll be happy to answer them, and
then we can discuss documentation updates wherever you feel
more documentation is needed.

Bottom line: Just make sure your patches get reviewed and approved
before the tentative branch time, and there will be no problem.
It looks like it's well under way for your patches.

-- 
Joel


  reply	other threads:[~2011-11-11  2:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 17:54 Joel Brobecker
2011-11-08 17:30 ` Tom Tromey
2011-11-09 15:13   ` Joel Brobecker
2011-11-09 19:41     ` Stan Shebs
2011-11-09  7:34 ` Tristan Gingold
2011-11-09 15:11   ` Joel Brobecker
2011-11-09 19:17 ` Jeremy Bennett
2011-11-09 19:23   ` Joel Brobecker
2011-11-10 10:10 ` Yao Qi
2011-11-10 15:43   ` Joel Brobecker
2011-11-11  2:18     ` Yao Qi
2011-11-11  2:34       ` Joel Brobecker [this message]
2011-11-11  5:58         ` Yao Qi
2011-11-11  2:42     ` Stan Shebs

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

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

  git send-email \
    --in-reply-to=20111111023407.GE5390@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.com \
    /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