From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] merge windows, package submission standards, procedure ... ?
Date: Wed, 30 May 2012 23:28:06 +0200 [thread overview]
Message-ID: <20120530232806.0b3365ec@skate> (raw)
In-Reply-To: <87d35lxtts.fsf@macbook.be.48ers.dk>
Le Wed, 30 May 2012 23:06:07 +0200,
Peter Korsgaard <jacmet@sunsite.dk> a ?crit :
> David> 1. a specific merge window/timeline that patches need to be
> David> in by in order to make it into a pending release?
>
> Yes. We do releases every 3 months (I'll most likely release 2012.05
> tonight). After a release has been done, the tree is open for new
> features for the next 2 months, after which I put of release
> (n+1)-rc1, and no longer add any new features to the main (release)
> branch. At the same time I also create a next branch and start adding
> new feature patches for the following release. Once the release is
> out I'll merge next to the the main branch and the cycle restarts.
Which means that practically speaking, you can send your patches at any
time, without having to worry about whether a merge window is opened or
not.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-30 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 21:51 [Buildroot] merge windows, package submission standards, procedure ... ? David Purdy
2012-05-30 21:06 ` Peter Korsgaard
2012-05-30 21:28 ` Thomas Petazzoni [this message]
2012-05-30 21:29 ` 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=20120530232806.0b3365ec@skate \
--to=thomas.petazzoni@free-electrons.com \
--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