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

[Martin Jansa]

On Thu, Dec 03, 2015 at 12:51:22PM +0000, Burton, Ross wrote:
> On 3 December 2015 at 11:43, Barros Pena, Belen <belen.barros.pena at intel.com
> > 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.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151203/ca079d7b/attachment-0002.sig>