From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] merge windows, package submission standards, procedure ... ?
Date: Wed, 30 May 2012 23:06:07 +0200 [thread overview]
Message-ID: <87d35lxtts.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAPOFwxoH3mJX8-tY0KvBiiyeH19VODTz+xgRMz=8-oB7q=154Q@mail.gmail.com> (David Purdy's message of "Tue, 29 May 2012 16:51:01 -0500")
>>>>> "David" == David Purdy <david.c.purdy@gmail.com> writes:
Hi,
David> Hi all,
David> As I'd not submitted a package/patch to Buildroot before a few days
David> ago**, I'm asking if there is:
David> 1. a specific merge window/timeline that patches need to be in by in
David> 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.
David> 2. anything more specific coding requirements than what is listed
David> here? : http://buildroot.uclibc.org/buildroot.html#add_packages
David> [ like checkpatch.pl conformity, trial build for minimum number of
David> targets/archs ]
Nothing really specific. The kernel/u-boot checkpatch is for C code, not
the typical makefile / build system fixes we have in buildroot.
The new asciidoc based manual (make manual-html or
http://buildroot.net/downloads/manual/manual.html has some more details
than the old buildroot.html).
David> 3. any one single person that I need to get contact (like a "new
David> packages custodian)?
David> [at U-Boot for instance they have "custodians" who manage certain
David> aspects of the git tree]
Not really. Just post on the mailing list. I'm the maintainer so I will
be one committing the changes to the official tree, but several people
review patches besides me.
David> 4. a need to open a Bug Report for a new package?
No, please just post patches on the list.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-05-30 21:06 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 [this message]
2012-05-30 21:28 ` Thomas Petazzoni
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=87d35lxtts.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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