Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] renaming packages/ to recipes/
Date: Wed, 25 Feb 2009 14:48:56 -0600	[thread overview]
Message-ID: <49A5AEB8.7080909@dls.net> (raw)
In-Reply-To: <go4a60$eh8$1@ger.gmane.org>

Koen Kooi wrote:
> On 25-02-09 21:21, Koen Kooi wrote:
> 
>> I have some other intrusive proposals about shuffling things around in
>> TMP a bit (and out of TMP as well), standardizing on source locations
>> for source_distribute and sourcepkg, etc, but let's start with this easy
>> one.
> 
> What I meant to say is:
> 
> Let's bunch up all the proposals that get approved so we can have a flag
> day in a week or 3 to minimize documentation churn.

Good timing; I was just composing a separate RFC email, but instead I'll
add my thoughts to this thread, since what I will propose is very
similar to the "flag day" idea.

I'd like to propose that we adopt a monthly "Big Change Window" (insert
your favorite term instead, if you wish).  Many organizations do this to
manage changes to shared branches.  The idea is that non-critical, but
potentially disruptive, changes are all merged to the dev branch during
standard time-periods (e.g. the first week of each calendar month).

This would set expectations for all users and even the core developers;
don't sync during these periods if you aren't ready, or perhaps some
folks might make the decision about working on a branch or not based on
the proximity of the Big Change Window.

(BTW, +1 on the renaming of packages to recipes)

-Mike



  reply	other threads:[~2009-02-25 20:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 20:21 [RFC] renaming packages/ to recipes/ Koen Kooi
2009-02-25 20:27 ` Henning Heinold
2009-02-25 20:37 ` Koen Kooi
2009-02-25 20:48   ` Mike (mwester) [this message]
2009-02-25 21:00     ` Merge windows, was: " Koen Kooi
2009-02-25 21:15       ` Michael 'Mickey' Lauer
2009-02-25 21:22         ` Koen Kooi
2009-02-26  0:56           ` Otavio Salvador
2009-02-26  9:09       ` Yuri Bushmelev
2009-02-25 20:41 ` Denys Dmytriyenko
2009-02-25 20:54   ` Koen Kooi
2009-02-26  6:52   ` Sledz, Steffen
2009-02-26  8:24 ` Martyn Welch
2009-02-26 10:44 ` Marcin Juszkiewicz
2009-02-26 12:59   ` Bernhard Guillon
2009-02-26 15:38     ` Yuri Bushmelev
2009-02-26 16:44     ` Rolf Leggewie
2009-03-04 11:27       ` Andrea Adami
2009-05-17 23:35   ` Rolf Leggewie
2009-05-17 23:56     ` Tom Rini
2009-05-19 12:19     ` Frans Meulenbroeks
2009-05-19 13:02       ` Philip Balister
2009-05-19 13:33         ` Koen Kooi
2009-05-19 14:02       ` Elena of Valhalla
2009-05-19 14:32         ` Frans Meulenbroeks
2009-02-26 11:08 ` Robert Schuster
2009-02-26 13:43 ` Leon Woestenberg
2009-03-04 11:16 ` Koen Kooi
2009-03-04 15:30   ` Tom Rini
2009-03-04 16:38     ` Koen Kooi
2009-03-05 15:35   ` Otavio Salvador
2009-03-13 18:10   ` Rob Tow

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=49A5AEB8.7080909@dls.net \
    --to=mwester@dls.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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