From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr>
To: "S. Bosscher" <S.Bosscher@student.tudelft.nl>
Cc: 'Mike Stump ' <mrs@apple.com>,
'David Edelsohn ' <dje@watson.ibm.com>,
'Mark Mitchell ' <mark@codesourcery.com>,
'Gerald Pfeifer ' <pfeifer@dbai.tuwien.ac.at>,
"'gcc@gcc.gnu.org '" <gcc@gcc.gnu.org>
Subject: Re: Release schedule
Date: Mon, 30 Sep 2002 16:06:00 -0000 [thread overview]
Message-ID: <20020930222024.GB16742@gauvain.u-strasbg.fr> (raw)
In-Reply-To: <4195D82C2DB1D211B9910008C7C9B06F01F372C5@lr0nt3.lr.tudelft.nl>
On Mon, Sep 30, 2002 at 11:46:28PM +0200, S. Bosscher wrote:
> On Saturday, September 28, 2002, at 02:21 PM, Steven Bosscher wrote:
> >>> Because of the overlap between releases and development, GCC
> >>> developers are forced to make a choice
> >>
> >> Yes, and closing development branches in the weeks before branching
> >> would "help" them make the choice ;-)
> >
> > Or it would drive them back underground, where they were in the past.
>
> yeah yeah I know, this was meant to be sarcasm, note the smiley...
>
> FWIW I am all *against* freezing dev branches. GCC developers are
> volunteers, and taking away their fun projects is a bad thing.
>
Agree, we're not paid for doing this, thus we can spend time on what
_we_ consider to be of interest.
Even if you close our branches you'll not get more bug fixes...
> Still I also think there are too many development projects right now, and I
> also believe that it would be good to plan when these major improvements
> should be finished, no matter how hard that may be in a project that depends
> on the time of volunteers.
>
Why not having a per major improvment release instead of the current
strict release schedule?
We don't sell our product, so I don't see why we should be constrained
by a strict schedule release.
If you want to have a strict schedule on the mainline, then you have to allow
schedule-free development on branches.
Sebastian
next prev parent reply other threads:[~2002-09-30 22:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 16:02 S. Bosscher
2002-09-30 16:06 ` Pop Sébastian [this message]
2002-09-30 20:05 ` Joe Buck
2002-10-01 16:03 ` Stan Shebs
-- strict thread matches above, loose matches on Subject: below --
2002-09-28 13:06 Roger Sayle
2002-09-25 11:53 Mark Mitchell
2002-09-25 11:55 ` Dale Johannesen
2002-09-25 12:42 ` Michael Matz
2002-09-29 12:07 ` Richard Henderson
2002-09-30 7:21 ` Michael Matz
2002-09-25 13:19 ` David Edelsohn
2002-09-25 13:53 ` Frank Ch. Eigler
2002-09-25 14:45 ` Geoff Keating
2002-09-25 15:05 ` Devang Patel
2002-09-26 11:45 ` Eric Botcazou
2002-09-25 13:43 ` David S. Miller
2002-09-26 3:32 ` David S. Miller
2002-09-25 16:00 ` David Edelsohn
2002-09-29 12:58 ` Richard Henderson
2002-09-26 2:03 ` Richard Earnshaw
2002-09-26 9:25 ` Alexander Kabaev
2002-09-26 14:46 ` Florian Weimer
2002-09-26 14:59 ` Joseph S. Myers
2002-09-26 15:16 ` Zack Weinberg
2002-09-28 7:41 ` Gerald Pfeifer
2002-09-28 7:54 ` Gerald Pfeifer
2002-09-28 10:06 ` Mark Mitchell
2002-09-28 13:26 ` David Edelsohn
2002-09-28 14:52 ` Steven Bosscher
2002-09-28 16:00 ` David Edelsohn
2002-09-30 10:34 ` Mike Stump
2002-09-30 9:20 ` Richard Zidlicky
2002-09-30 10:30 ` Andrew Pinski
2002-04-26 0:30 Release Schedule Jim Blomo
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=20020930222024.GB16742@gauvain.u-strasbg.fr \
--to=pop@gauvain.u-strasbg.fr \
--cc=S.Bosscher@student.tudelft.nl \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=mrs@apple.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).