OE-Classic patches in patchwork

OE-Classic patches in patchwork

[Paul Eggleton]

Hi all,

There is a significant volume of patches in the OE patchwork [1] that are 
intended to apply to OE-Classic. Apart from the 2011.3-maintenance branch, OE-
Classic is no longer maintained in favour of OE-Core + layers, so the question 
is what should we do with these patches? At the moment I'm thinking we should 
just mark them as "archived" so that they disappear from the queue; people can 
still get access to them if needed.

Thoughts?

Cheers,
Paul

[1] http://patchwork.openembedded.org/project/oe/list/

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: OE-Classic patches in patchwork

[Otavio Salvador]

On Tue, Dec 4, 2012 at 4:11 PM, Paul Eggleton <paul.eggleton@linux.intel.com
> wrote:

> There is a significant volume of patches in the OE patchwork [1] that are
> intended to apply to OE-Classic. Apart from the 2011.3-maintenance branch,
> OE-
> Classic is no longer maintained in favour of OE-Core + layers, so the
> question
> is what should we do with these patches? At the moment I'm thinking we
> should
> just mark them as "archived" so that they disappear from the queue; people
> can
> still get access to them if needed.
>
> Thoughts?
>

I fully agree.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: OE-Classic patches in patchwork

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

On Tue, Dec 04, 2012 at 06:11:22PM +0000, Paul Eggleton wrote:
> Hi all,
> 
> There is a significant volume of patches in the OE patchwork [1] that are 
> intended to apply to OE-Classic. Apart from the 2011.3-maintenance branch, OE-
> Classic is no longer maintained in favour of OE-Core + layers, so the question 
> is what should we do with these patches? At the moment I'm thinking we should 
> just mark them as "archived" so that they disappear from the queue; people can 
> still get access to them if needed.
> 
> Thoughts?

There is also 70 patches from chase maupin just updating LICENSE to
contain also version.

I'm not using oe-classic anymore, but I believe he prepared them
carefully and it's worth merging.

I'll create bundle from it and apply it tomorrow if nobody objects.

Cheers,

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: OE-Classic patches in patchwork

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 4026 bytes --]

On Fri, Dec 14, 2012 at 12:20:58AM +0100, Martin Jansa wrote:
> On Tue, Dec 04, 2012 at 06:11:22PM +0000, Paul Eggleton wrote:
> > Hi all,
> > 
> > There is a significant volume of patches in the OE patchwork [1] that are 
> > intended to apply to OE-Classic. Apart from the 2011.3-maintenance branch, OE-
> > Classic is no longer maintained in favour of OE-Core + layers, so the question 
> > is what should we do with these patches? At the moment I'm thinking we should 
> > just mark them as "archived" so that they disappear from the queue; people can 
> > still get access to them if needed.
> > 
> > Thoughts?
> 
> There is also 70 patches from chase maupin just updating LICENSE to
> contain also version.
> 
> I'm not using oe-classic anymore, but I believe he prepared them
> carefully and it's worth merging.
> 
> I'll create bundle from it and apply it tomorrow if nobody objects.

Can we fix patchwork to show bundles marked as public to public users?

I've few bundles
Name	Project	Public Link	Patches	Download	Delete
in-test		oe	http://patches.openembedded.org/bundle/jama/in-test/	21		
oe-classic	oe 	http://patches.openembedded.org/bundle/jama/oe-classic/	61		
oe-classic-lic	oe 	http://patches.openembedded.org/bundle/jama/oe-classic-lic/	70		
2011.03-maintenance oe	http://patches.openembedded.org/bundle/jama/2011.03-maintenance/	1		
denzil		oe	http://patches.openembedded.org/bundle/jama/denzil/	6		
danny		oe	http://patches.openembedded.org/bundle/jama/danny/	5		
meta-handheld	oe	http://patches.openembedded.org/bundle/jama/meta-handheld/	1		
meta-java	oe	http://patches.openembedded.org/bundle/jama/meta-java/	15		
meta-opie	oe	http://patches.openembedded.org/bundle/jama/meta-opie/	1		

But without sharing link to bundle, nobody will find it (AFAIK) maybe
there is newer version of Patchwork which shows public bundles
somewhere?

oe-classic bundle is now marked as archived - so not listed by default.
oe-classic-lic also marked as archived and I'll apply it later today.

It would be great if we agree to mark patches as archived when they get assigned 
to some bundle to keep main patchwork list relatively clean and layer/release 
maintainers can still see all patches with "New" state in corresponding bundle.

I've also marked some patches with review comments without reply as
"Changes requested" + archived. Pity that some patches had rather
trivial issues, but submitter never responded with v2..

And there were some patches for oe-core already applied in oe-core.. so
marked as "Not applicable" + archived.

I'm testing few more patches from PW in world build, some with small modifications:
pick ba53658 udev: remove from meta-oe
pick 04c9cd0 modemmanager: update to 0.6.0.0
pick 00d02ae samba: added gnu-configize for AArch64 support
pick e793760 dialog: added gnu-configize for AArch64 support
pick c1d541c xterm: added gnu-configize for AArch64 support
pick 1bc2922 florence: added gnome-doc-utils and libnotify to dependencies
pick 66b86e2 meta-oe: Fix erroneous use of "startline" in LIC_FILES_CHKSUM
pick 0caaf89 meta-networking: Fix erroneous use of "startline" in LIC_FILES_CHKSUM
pick 36d093e libnl: remove
pick a8f4d0c gtk+3: add libxi dependency
pick 7506e1c libsdl-image: update to upstream version 1.2.12
pick 0480f25 samba: Fix build on Fedora 17
pick 437acf3 fakeroot: update to upstream version 1.18.4
pick 852e1cf python-numpy: add missing runtime dependencies
pick c538fa9 geos: add recipe
pick 56fe334 libspatialite: add recipe
pick f0f428e wpa-supplicant, gcc-common-4.6, packagegroup-qte-toolchain-target: use correct PRINC form
pick a254473 lua: update to upstream version 5.1.5
pick a89eaca postgresql: disable spinlocks for AArch64
pick 5f1b851 libgcc: s/virtclass/class/ to make it up-to-date
pick 62895de gcc-cross-canadian 4.6: fix dependencies to be nativesdk-* not *-nativesdk
pick e0f0453 Add recipe for krb5

Cheers,

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Archived patchwork entries Was: OE-Classic patches in patchwork

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 4506 bytes --]

On Fri, Dec 14, 2012 at 12:05:07PM +0100, Martin Jansa wrote:
> On Fri, Dec 14, 2012 at 12:20:58AM +0100, Martin Jansa wrote:
> > On Tue, Dec 04, 2012 at 06:11:22PM +0000, Paul Eggleton wrote:
> > > Hi all,
> > > 
> > > There is a significant volume of patches in the OE patchwork [1] that are 
> > > intended to apply to OE-Classic. Apart from the 2011.3-maintenance branch, OE-
> > > Classic is no longer maintained in favour of OE-Core + layers, so the question 
> > > is what should we do with these patches? At the moment I'm thinking we should 
> > > just mark them as "archived" so that they disappear from the queue; people can 
> > > still get access to them if needed.
> > > 
> > > Thoughts?
> > 
> > There is also 70 patches from chase maupin just updating LICENSE to
> > contain also version.
> > 
> > I'm not using oe-classic anymore, but I believe he prepared them
> > carefully and it's worth merging.
> > 
> > I'll create bundle from it and apply it tomorrow if nobody objects.
> 
> Can we fix patchwork to show bundles marked as public to public users?
> 
> I've few bundles
> Name	Project	Public Link	Patches	Download	Delete
> in-test		oe	http://patches.openembedded.org/bundle/jama/in-test/	21		
> oe-classic	oe 	http://patches.openembedded.org/bundle/jama/oe-classic/	61		
> oe-classic-lic	oe 	http://patches.openembedded.org/bundle/jama/oe-classic-lic/	70		
> 2011.03-maintenance oe	http://patches.openembedded.org/bundle/jama/2011.03-maintenance/	1		
> denzil		oe	http://patches.openembedded.org/bundle/jama/denzil/	6		
> danny		oe	http://patches.openembedded.org/bundle/jama/danny/	5		
> meta-handheld	oe	http://patches.openembedded.org/bundle/jama/meta-handheld/	1		
> meta-java	oe	http://patches.openembedded.org/bundle/jama/meta-java/	15		
> meta-opie	oe	http://patches.openembedded.org/bundle/jama/meta-opie/	1		
> 
> But without sharing link to bundle, nobody will find it (AFAIK) maybe
> there is newer version of Patchwork which shows public bundles
> somewhere?
> 
> oe-classic bundle is now marked as archived - so not listed by default.
> oe-classic-lic also marked as archived and I'll apply it later today.
> 
> It would be great if we agree to mark patches as archived when they get assigned 
> to some bundle to keep main patchwork list relatively clean and layer/release 
> maintainers can still see all patches with "New" state in corresponding bundle.
> 
> I've also marked some patches with review comments without reply as
> "Changes requested" + archived. Pity that some patches had rather
> trivial issues, but submitter never responded with v2..
> 
> And there were some patches for oe-core already applied in oe-core.. so
> marked as "Not applicable" + archived.

Andrea just asked about this, so if someone missed this information:

There are some bundles:
2011.03-maintenance oe	http://patches.openembedded.org/bundle/jama/2011.03-maintenance/	1		
danny		oe	http://patches.openembedded.org/bundle/jama/danny/			9		
denzil		oe	http://patches.openembedded.org/bundle/jama/denzil/			10		
in-test		oe	http://patches.openembedded.org/bundle/jama/in-test/			161		
meta-browser	oe	http://patches.openembedded.org/bundle/jama/meta-browser/		7		
meta-handheld	oe	http://patches.openembedded.org/bundle/jama/meta-handheld/		2		
meta-initramfs	oe	http://patches.openembedded.org/bundle/jama/meta-initramfs/		1		
meta-java	oe	http://patches.openembedded.org/bundle/jama/meta-java/			15		
meta-kde	oe	http://patches.openembedded.org/bundle/jama/meta-kde/			1		
meta-networking	oe	http://patches.openembedded.org/bundle/jama/meta-networking/		12		
meta-opie	oe	http://patches.openembedded.org/bundle/jama/meta-opie/			2		
meta-systemd	oe	http://patches.openembedded.org/bundle/jama/meta-systemd/		25		
meta-webserver	oe	http://patches.openembedded.org/bundle/jama/meta-webserver/		2		
oe-classic	oe	http://patches.openembedded.org/bundle/jama/oe-classic/			62		
oe-classic-lic	oe	http://patches.openembedded.org/bundle/jama/oe-classic-lic/		70		

I'm adding patches to right bundle when I'm sorting patches to 
test them on jenkins (in-test bundle, contrib/jansa/in-test branch).

In the process I'm marking them as "Archived" (to see what's not sorted in main page), 
but because their state stays "New" you can still find them in bundles, e.g.
http://patches.openembedded.org/bundle/jama/meta-webserver/?archive=both

Cheers,

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]