All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: Maintenance on older branches, e.g. bernard
Date: Wed, 08 Aug 2012 11:39:50 -0700	[thread overview]
Message-ID: <5022B276.7000104@intel.com> (raw)
In-Reply-To: <22F5AB9F-5063-4443-97B6-B88EA9DAE877@gmail.com>

On 08/08/2012 11:20 AM, Elvis Dowson wrote:
> Hi, I just noticed that if one were to try switching to an older poky
> branch, say bernard, there are a few errors:
>
> e.g. meta-yocto layer doesn't have a conf folder.
>
> Also if you use one of the tags, e.g. bernard-5.0, bernard-5.0.1,
> bernard-5.0.2, you can run into build failures.
>
> I think at the very least, one should be able to build successfully
> off one of the older branches, and perhaps it should be part of the
> regular regression tests?

When you say "build successfully", how do you define that? Building 
core-image-minimal? -sato? -lsb? For which machines? On how many host 
distros?

We have a problem of scale here which is why bernard (now three stable 
releases old) is no longer undergoing active maintenance or regression 
testing by the core team.

This is where the community or a partner organization with a financial 
interest in supporting that release for their customers needs to step 
in. As time goes on, we're seeing more commercial adoption our releases 
and I think we'll see more of this for the recent releases (edison and 
denzil in particular, but bernard came out when the Yocto Project was 
still fairly new).

IMO,

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


  reply	other threads:[~2012-08-08 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 18:20 Maintenance on older branches, e.g. bernard Elvis Dowson
2012-08-08 18:39 ` Scott Garman [this message]
2012-08-08 18:52   ` Elvis Dowson

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=5022B276.7000104@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.