Re: [OE-core] [Openembedded-architecture] Patchwork & patch handling improvements

[Burton, Ross]

On 3 December 2015 at 11:43, Barros Pena, Belen  wrote:

> >and more status values.
>
> You can add status values (to the db directly or via the Django admin
> interface), but they will apply to all projects in the Patchwork instance.
> Ideally you should be able to set a list of status values per project I
> guess.
>

Well it depends on what the extra values are.  Martin, what values do you
use?  A "merged in staging" value would be useful for everyone.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Patchwork & patch handling improvements

[Barros Pena, Belen]

On 02/12/2015 18:43, "Burton, Ross"  wrote:

>
>On 2 December 2015 at 18:04, Martin Jansa
> wrote:
>
>I'm depending on bundles heavily, to "mark" the patches for layers with
>dedicated maintainer and also for extra "status" like merged in
>"master-next" branch for jenkins build, because standard status values
>aren't fine-grained enough.
>
>
>
>
>Sounds like instead of bundles the new patchworks needs the ability for a
>single list to represent multiple projects (so there'd be a meta-oe,
>meta-python, etc),

That's already in place

https://github.com/dlespiau/patchwork/issues/15

>and more status values.

You can add status values (to the db directly or via the Django admin
interface), but they will apply to all projects in the Patchwork instance.
Ideally you should be able to set a list of status values per project I
guess. 

Cheers

Belén

>
>
>Ross
>

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Patchwork & patch handling improvements

[Martin Jansa]

On Thu, Dec 03, 2015 at 12:51:22PM +, Burton, Ross wrote:
> On 3 December 2015 at 11:43, Barros Pena, Belen  > wrote:
> 
> > >and more status values.
> >
> > You can add status values (to the db directly or via the Django admin
> > interface), but they will apply to all projects in the Patchwork instance.
> > Ideally you should be able to set a list of status values per project I
> > guess.
> >
> 
> Well it depends on what the extra values are.  Martin, what values do you
> use?  A "merged in staging" value would be useful for everyone.

The list of bundles is in:
http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork

Once the patches are added to correct bundles I mark them as archived to
know which ones were sorted (the main page gets empty).

Advantage of bundles (something similar can probably work with tags) is
that the same patch can be in multiple bundles, e.g. I can include some
change in master-next branch and bundle while also adding it to
meta-networking bundle for Joe to merge it when ready.

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Patchwork & patch handling improvements

[Barros Pena, Belen]

On 03/12/2015 12:51, "Burton, Ross"  wrote:

>On 3 December 2015 at 11:43, Barros Pena, Belen
> wrote:
>
>>and more status values.
>
>You can add status values (to the db directly or via the Django admin
>interface), but they will apply to all projects in the Patchwork instance.
>Ideally you should be able to set a list of status values per project I
>guess.
>
>
>
>
>Well it depends on what the extra values are.

Heh, I meant that's how Patchwork works at the moment, independently of
what we do for OE


> Martin, what values do you use?  A "merged in staging" value would be
>useful for everyone.
>
>
>Ross
>

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Patchwork & patch handling improvements

[Burton, Ross]

On 2 December 2015 at 18:04, Martin Jansa  wrote:

> I'm depending on bundles heavily, to "mark" the patches for layers with
> dedicated maintainer and also for extra "status" like merged in
> "master-next" branch for jenkins build, because standard status values
> aren't fine-grained enough.
>

Sounds like instead of bundles the new patchworks needs the ability for a
single list to represent multiple projects (so there'd be a meta-oe,
meta-python, etc), and more status values.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Patchwork & patch handling improvements

[Tim Orling]

On Wed, Dec 2, 2015 at 10:43 AM, Burton, Ross  wrote:

>
> On 2 December 2015 at 18:04, Martin Jansa  wrote:
>
>> I'm depending on bundles heavily, to "mark" the patches for layers with
>> dedicated maintainer and also for extra "status" like merged in
>> "master-next" branch for jenkins build, because standard status values
>> aren't fine-grained enough.
>>
>
> Sounds like instead of bundles the new patchworks needs the ability for a
> single list to represent multiple projects (so there'd be a meta-oe,
> meta-python, etc), and more status values.
>
> I agree with Ross that if we can get the functionality we truly need into
Patchwork--and JaMa can live with the result or help guide the
functionality--that we have a better path into the future.

Also, for what it's worth I vote for spaces only. We can provide editor
templates/settings to make it easy on the end users. There are languages
that require tabs, there are languages that require spaces. Deal with the
required tabs when the necessary evil arises.

--Tim

>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core