From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developer Day
Date: Wed, 02 Nov 2011 21:15:46 +0100 [thread overview]
Message-ID: <87liryjn65.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20111102160349.4afe5935@skate> (Thomas Petazzoni's message of "Wed, 2 Nov 2011 16:03:49 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
Thomas> Buildroot Developer Day - ELCE 2011
Thomas> ===================================
Thomas> The Embedded Linux Conference Europe 2011 took place from Wednesday
Thomas> October, 26th to Friday October, 28th in Prague. The Buildroot
Thomas> developers took that opportunity to organize a one day meeting on
Thomas> Saturday October, 29th. The meeting took place in the lobby of the
Thomas> Clarion Congress Hotel, where the rest of the conference took place.
Thanks a lot for the writeup Thomas!
Thomas> * The development process has a 3 months cycle, with 2 months of
Thomas> development and 1 month of bug-fixing. During the month of
Thomas> bug-fixing, Peter only accepts bug fix patches and other minor
Thomas> evolutions. This means that the merge of more invasive patches is
Thomas> completely stalled during one month and those patches accumulate
Thomas> and it is difficult for Peter to merge them all when the next
Thomas> development cycle opens. To solve this, Peter will now maintain a
Thomas> -next branch during the month of bug-fixing. This way, Peter will
Thomas> continue to merge the patches non-acceptable during the bug-fixing
Thomas> period, and all those patches would be merged into the master
Thomas> branch as soon as the next development cycle starts.
Which means I'm running late for 2011.11-rc1 because of ELCE and other
real life stuff. I was hoping to be able to put out rc1 today, as I'll
be away for the rest of the week - But that's not going to happen.
Expect rc1 early next week instead. If you have any pending patches you
think should go into rc1, please ping me.
Once rc1 is out, then I'll create the -next branch and start merging in
new stuff.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-11-02 20:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 15:03 [Buildroot] Report from the Buildroot Developer Day Thomas Petazzoni
2011-11-02 20:15 ` Peter Korsgaard [this message]
2011-11-04 11:56 ` Luca Ceresoli
2011-11-04 12:30 ` Michael S. Zick
2011-11-07 16:17 ` Peter Korsgaard
2011-11-07 9:58 ` Thomas De Schampheleire
2011-11-07 12:09 ` Sam Ravnborg
2011-11-07 12:25 ` Thomas Petazzoni
2011-11-07 12:39 ` Yann E. MORIN
2011-11-08 13:20 ` Thomas De Schampheleire
2011-11-07 12:39 ` Thomas Petazzoni
2011-11-07 19:01 ` Yann E. MORIN
2011-11-08 8:19 ` Thomas De Schampheleire
2011-11-15 22:17 ` Arnout Vandecappelle
2011-11-15 23:28 ` Michael S. Zick
2011-11-17 13:57 ` Thomas De Schampheleire
2011-11-17 21:21 ` Bjørn Forsman
2011-11-18 6:39 ` Thomas De Schampheleire
2011-11-18 11:04 ` Bjørn Forsman
2011-11-18 11:36 ` Thomas De Schampheleire
2011-11-18 17:51 ` Arnout Vandecappelle
2011-11-18 22:53 ` Peter Korsgaard
2011-11-18 23:16 ` Arnout Vandecappelle
2011-11-19 8:24 ` Peter Korsgaard
2011-11-20 8:36 ` Thomas Petazzoni
2011-11-20 9:58 ` Peter Korsgaard
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=87liryjn65.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.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