[oe] Reconsidering the work flow and how the SCM system fits in

[Paul Sokolovsky]

Hello,

On Tue, 11 Mar 2008 09:47:19 +0100
Esben Haabendal <EsbenHaabendal at gmail.com> wrote:

[]

> > comments? agreement?
> >   
> Without going into the specifics of the SCM tools discussion, I would
> just like to say that I would REALLY REALLY love to see branches being
> used actively in OE development, 

Oh really? Because I would think that loving to see them makes little
sense. It makes sense only to use them. And who will use them?
Because if people wanted to use them, they would do that already.
Actually, people who want, do.

> especially for feature development
> (such as sysroot, packaged-staging, and so on) and for release
> engineering.
> 
> For OE to really reach it's potential we have to be able add even more
> features while at the same time delivering stable releases/branches
> for distro and product developers to work from.
> 
> When Joe-average-embedded-product-developer comes along, shopping for
> which embedded Linux tool to use for his embedded product, he really
> should be able to checkout a stable version of OE and be able to
> build a toolchain and a simple image for all supported targets. And
> this is certainly not the situation right now.

Typical mistake. There's stable branch in OE, and based on the
experience with the previous branches, best-practices change control
procedure was applied to it. Now, based on 2.5 month existence of that
branch, I have following observations:

1. People don't know about that branch.
2. Once made known, people still pretend that there's none, and
continue to complain about stability.
3. Most of the rest of people don't put slightest effort into
maintenance of that branch.
4. Those who try, complain that the change control procedure is ...
complex! But it is only a separate branch + pre-review of changes + "all
changes are merged from main branch" rule of thumb.


Having more branches is not going to help with this at all. 

> 
> /Esben

[]

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