All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC agenda items for the next meeting
Date: Mon, 14 Feb 2011 09:08:47 +0100	[thread overview]
Message-ID: <AANLkTi=FjYGco4xmNaE_2hFdWMr9Br3b3wCG1zZ_f4YB@mail.gmail.com> (raw)
In-Reply-To: <4D585D07.70305@xora.org.uk>

2011/2/13 Graeme Gregory <dp@xora.org.uk>:
> On 13/02/2011 10:50, Koen Kooi wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> The new TSC is holding a meeting next week and we wanted to see if
>> anyone wants to suggest items we put in the agenda for the meeting.
>>
>> If you have such items, please let us know by replying to this mail.
>>
>> regards,
>>
>> Koen
>
> Re-inforcement of the "don't delete all old versions" policy, make sure this
> is in the wiki somewhere.

Not sure what you mean with re-inforcement and what policy you are referring to.
This topic has been discussed and decided by the TSC last may. See
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-May/020047.html
For now I haven't really heard reasons to deviate from it, and I think
there are more important things requiring the TSCs attention (like the
ones you mention below).
But I feel it is a good plan to make this policy more explicit in the
wiki, it is now somewhat hidden.

Then again if we work more towards releases the reasons for keeping
old versions might be less relevant.
and of course we could also decide to keep old versions in a separate layer.

What I QA wise would like to see is that all recipes (also old
versions) fetch and are building (for the archs/distros they are
intended for).
Non building recipes create a bad impression quite quickly.

Frans

>
> Rough Yocto integration plan.
>
> Start to think about the Policies section on wiki and whether it is
> relevant/correct now, and also what needs to change going forward to Yocto.
>
> Graeme
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



  reply	other threads:[~2011-02-14  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13 10:50 TSC agenda items for the next meeting Koen Kooi
2011-02-13 21:38 ` Philip Balister
2011-02-13 22:36 ` Graeme Gregory
2011-02-14  8:08   ` Frans Meulenbroeks [this message]
2011-02-14  6:58 ` Frans Meulenbroeks
2011-02-14  9:16 ` Yury Bushmelev
2011-02-14  9:48 ` Stefan Schmidt
2011-02-14 10:55   ` Graeme Gregory
2011-02-14 13:33   ` Frans Meulenbroeks
2011-02-14 14:18     ` Stefan Schmidt

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='AANLkTi=FjYGco4xmNaE_2hFdWMr9Br3b3wCG1zZ_f4YB@mail.gmail.com' \
    --to=fransmeulenbroeks@gmail.com \
    --cc=openembedded-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 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.