Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: 1.16 stable series
Date: Thu, 01 Nov 2012 06:14:35 +0000	[thread overview]
Message-ID: <1351750475.6502.11.camel@ted> (raw)

One of the issues with previous OE-Core and Poky releases has been
deciding which bitbake should be used used with them. There is a copy of
bitbake in poky denzil which is a now becoming a bit of a Frankenstein,
not corresponding to any particular bitbake release with various random
patches from master. This isn't necessarily a bad thing and users of
poky find it useful but I think we can do better.

This time around, for the danny series I made sure we had a bitbake
stable branch available to correspond with it (1.16). I'm planning to
use the 1.16 branch as a stable bitbake branch and directly include that
in poky-danny verbatim. So far I don't think there have been any
invasive changes on master so I might just push current master into the
1.16 branch. As development moves forward, we'd move to a model of
picking specific commits that make sense for the branch.

I really just wanted to let people know what I was intending here, I
doubt its too controversial and if people have specific things they want
to see in the stable branch, feel free to point them out!

Cheers,

Richard









             reply	other threads:[~2012-11-01 10:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01  6:14 Richard Purdie [this message]
2012-11-01 22:08 ` 1.16 stable series McClintock Matthew-B29882
2012-11-02 17:52   ` Richard Purdie

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=1351750475.6502.11.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    /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