Stable versions of OE

Stable versions of OE

[Nelson Castillo]

Hi.

I've been following this document (http://wiki.emqbit.com//openembedded)
by Stefano Parusso that explains how to build OE for a ARM board[1].

It works for the snapshot for November the 7th and not for the most recent
one. I read in the Getting Started wiki page[3]:

  Once you have a "known good" version that works well on your
  system, keep it! To update, clone a new copy; don't overwrite
  that working version until it's known to be safe.

So, I guess it means I should stay with the old metadata.

My questions are:

  * Does OE ever do "stable" releases?

  * If not, how do you make "stable" releases for yur plataforms?

Regards,
Nelson.-

[1] http://wiki.emqbit.com/free-ecb-at91
[2] http://www.openembedded.org/snapshots/OE-this-is-for-mtn-0.30.mtn.bz2
[3] http://www.openembedded.org/wiki/GettingStarted

-- 
 http://arhuaco.org
http://emQbit.com

Re: Stable versions of OE

[Cliff Brake]

On 1/29/07, Nelson Castillo <nelson@emqbit.com> wrote:
> Hi.
>
> I've been following this document (http://wiki.emqbit.com//openembedded)
> by Stefano Parusso that explains how to build OE for a ARM board[1].
>
> It works for the snapshot for November the 7th and not for the most recent
> one. I read in the Getting Started wiki page[3]:
>
>   Once you have a "known good" version that works well on your
>   system, keep it! To update, clone a new copy; don't overwrite
>   that working version until it's known to be safe.
>
> So, I guess it means I should stay with the old metadata.

Current versions of OE are quite stable for ARM.  Chances are you have
something configured incorrectly.  Hop on the IRC channel and post the
error and it will probably be easy to fix.

> My questions are:
>
>   * Does OE ever do "stable" releases?

Not that I know of.

>   * If not, how do you make "stable" releases for yur plataforms?

I generally follow the tip of dev early in the development.  At some
point once things are working pretty well, I record the version of the
OE meta data and bitbake I am using and then stick with it.  I can
still update the database, but I always make sure I check out that
revision.  This brings up a good question -- are the revision hashs in
OE valid forever?

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com

Re: Stable versions of OE

[Holger Freyther]

Am 29.01.2007 um 20:26 schrieb Cliff Brake:

> This brings up a good question -- are the revision hashs in
> OE valid forever?

They changed during the 0.26 rosterify. So it might be a good idea to  
tag them?

h.

Re: Stable versions of OE

[Paul Sokolovsky]

Hello Nelson,

Monday, January 29, 2007, 7:40:11 PM, you wrote:

> Hi.

> I've been following this document
> (http://wiki.emqbit.com//openembedded)
> by Stefano Parusso that explains how to build OE for a ARM board[1].

> It works for the snapshot for November the 7th and not for the most recent
> one. I read in the Getting Started wiki page[3]:

>   Once you have a "known good" version that works well on your
>   system, keep it! To update, clone a new copy; don't overwrite
>   that working version until it's known to be safe.

> So, I guess it means I should stay with the old metadata.

> My questions are:

>   * Does OE ever do "stable" releases?

    OE is a kind of "meta-distribution". To the large part, it leaves
definition of what is stable to specific distributions which are based
on it.

>   * If not, how do you make "stable" releases for yur plataforms?

    By creating branches for specific distributions. For example,
there's a branch for OpenZaurus. As OE uses distributed SCM, you more
or less easily can create and maintain your own private branch, merge
to it from .dev only what you consider stable for you. Even without
creating branch, you can get reasonable level of stability by
pinpointing versions of packages you like to use (in this case you
however at least depend on those versions not being removed, and old
stuff is regularly cleaned up from .dev)

> Regards,
> Nelson.-



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com

Re: Stable versions of OE

[Michael 'Mickey' Lauer]

Nelson Castillo wrote:
> My questions are:
>   * Does OE ever do "stable" releases?

Soon. During the first OEDEM we decided to prepare quarterly
snapshots. We just dont't have the necessary infrastructure
(stabilization phases, unit tests) for that in place yet.

>   * If not, how do you make "stable" releases for yur plataforms?

I start off with a snapshot and then integrate relevant changes from
later revisions by monotone "cherry picking".

Regards,

:M:
-- 
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de

Re: Stable versions of OE

[Nelson Castillo]

On 1/29/07, Michael 'Mickey' Lauer <mickey@vanille-media.de> wrote:
> Nelson Castillo wrote:
> > My questions are:
> >   * Does OE ever do "stable" releases?
>
> Soon. During the first OEDEM we decided to prepare quarterly
> snapshots. We just dont't have the necessary infrastructure
> (stabilization phases, unit tests) for that in place yet.

This will be nice.

> >   * If not, how do you make "stable" releases for yur plataforms?
>
> I start off with a snapshot and then integrate relevant changes from
> later revisions by monotone "cherry picking".

Thanks. Well, we'll do that and when ready (catching up with
the latest snapshot) we will send the files for the new board
asking you to include them. We might ask for help if needed.

Thank you all for your replies,
Nelson.-  (Who will start following this mailing list from today).

-- 
http://arhuaco.org
http://emQbit.com