Strategies for push/merge problem?

[Sean Kelley]

Hi

On Mon, Jul 14, 2008 at 8:40 PM, Douglas Philips <dgou at mac.com> wrote:
> On 2008 Jul 14, at 9:26 PM, Sean Kelley wrote:
>> different and varying projects.  In our case, no one 'owns' particular
>> repos.  On any given day of the week, you may be working on different
>> products that have varying projects that make up its build.  It would
>> be incredibly unproductive to tether someone to a particular repo that
>> may only be used once for maybe three products.  We are an enterprise
>> level development house that pushes out embedded products.
>
> If you don't mind my asking, it sounds very chaotic, how is product
> testing/quality-control done?

We use release branches of PokyLinux.  A release branch of the
PokyLinux build system freezes the tag versions pulled from the source
repos that make up the embedded Linux product.  We also use release
branches within HG repos.  Poky is our software configuration
management tool leveraging Mercurial release branches and tags.
PokyLinux consists of many recipes - bitbake script files with recipes
that pull from explicit tags of some of the many repos.  By tagging
our Poky repo we can do a development release.  By cloning the
mainline Poky repo we can create release branches off of those tags.

http://www.pokylinux.org/

Sean


Sean


>
> --Doug
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>