Patchwork cleanup weekend in two days

Patchwork cleanup weekend in two days

[Stefan Schmidt]

Hello.

Its time for some house-keeping again. I know many people are working on
patchwork on-going, thanks for that.

Looking throught it during OEDEM did still show up way to many entries. Some are
still from 2009. Next Saturday and Sunday I would like to reduce our  current
count from 273 patches. 100 or less would be a nice goal imho.

Steps to help out:
1) make sure you have a patchwork account and are added to the admin group to
   change patches
2) Hang out on IRC on saturday and sunday
3) Go through the patchwork and find all patches from yourself and up date them
   with a current status. e.g. mark them as superseeded if you send a new version
   or applied if they hit the tree.
4) After your own patches pick other ones and try to find out about their
   current staus. Usually git log, the ml or asking people on IRC helps here to
   find out stuff about the patch.

If you cleaned up more then 10 patches a day you are allowed to drink a beer in
the evening. ;)

regards
Stefan Schmidt

Re: Patchwork cleanup weekend in two days

[Frans Meulenbroeks]

2010/11/4 Stefan Schmidt <stefan@datenfreihafen.org>:
> Hello.
>
> Its time for some house-keeping again. I know many people are working on
> patchwork on-going, thanks for that.
>
> Looking throught it during OEDEM did still show up way to many entries. Some are
> still from 2009. Next Saturday and Sunday I would like to reduce our  current
> count from 273 patches. 100 or less would be a nice goal imho.
>
> Steps to help out:
> 1) make sure you have a patchwork account and are added to the admin group to
>   change patches
> 2) Hang out on IRC on saturday and sunday
> 3) Go through the patchwork and find all patches from yourself and up date them
>   with a current status. e.g. mark them as superseeded if you send a new version
>   or applied if they hit the tree.
> 4) After your own patches pick other ones and try to find out about their
>   current staus. Usually git log, the ml or asking people on IRC helps here to
>   find out stuff about the patch.
>
> If you cleaned up more then 10 patches a day you are allowed to drink a beer in
> the evening. ;)

I would love to help out, but as it stands I'll be travelling on
saturday and won't have internet access on sat and sun (and probably
the rest of the week neither)
(but I'll drink the beer anyway :-) ).
Wish you all the best cleaning up!

Frans

Re: Patchwork cleanup weekend in two days

[Frans Meulenbroeks]

Oh, one more thing,

Of course it is not up to me how you guys spent your time, but if
there is time and interest left after going through patchwork it would
be nice if people could also have a peek at bugzilla and/or peek at
the recipes that do not even fetch any more (see email from Martin
from april or so).

Have fun (& thanks for the effort!)
Frans

Re: Patchwork cleanup weekend in two days

[Stefan Schmidt]

Hello.

On Thu, 2010-11-04 at 09:27, Stefan Schmidt wrote:
> 
> Its time for some house-keeping again. I know many people are working on
> patchwork on-going, thanks for that.
> 
> Looking throught it during OEDEM did still show up way to many entries. Some are
> still from 2009. Next Saturday and Sunday I would like to reduce our  current
> count from 273 patches. 100 or less would be a nice goal imho.

We are no down to a patch count of 186. With the new patches that came in the
last two days that makes 100 patches that are gone. Most of them had already
been applied or superseded by other patches and often were just missing a status
update.

For the outstanding patches I see three big groups which need our attention:

1) Core/class patches: It would be great if some people more familiar with the
   core internals of OE could have a look at them and discuss outstanding issues
   or apply them.

2) Stable/2009 patches: We still have patches sitting in patchwork for the
   stable branch. It would be great if they also could get some attention, not
   only patches for master.

3) Outdated patches: We have patches reaching as far back as 2009. This needs
   improvement. Besides making sure that patches are getting review in a timely
   manner and really get applied when already acked we should think about
   patches that do not get and feedback at all.

As a side note the patchwork installation will move to our OSUOSL server. The
new installation will not hold the old patch history we have right now. This
should be taken as motivation to clean up the rest we have in there. :)

I have mixed feeling after this weekend. On the one hand we got rid of quite
some outstanding stuff on the other hand most of the changes have been updates
on the patch status and finding out if they have already been applied. Also only
a handfull people could get motivated to help. For the next incarnation of such
a weekend (I would aim for early december after the first release was tagged) it
would be great if more people could join the fun.

regards
Stefan Schmidt

Re: Patchwork cleanup weekend in two days

[Andreas Mueller]

On Sunday 07 November 2010 19:20:29 Stefan Schmidt wrote:
> Hello.
> 
> On Thu, 2010-11-04 at 09:27, Stefan Schmidt wrote:
> > 
> > Its time for some house-keeping again. I know many people are working on
> > patchwork on-going, thanks for that.
> 
/patch/2970/ was nak'd / superseded.

Andreas

Re: Patchwork cleanup weekend in two days

[Stefan Schmidt]

Hello.

On Mon, 2010-11-08 at 09:12, Andreas Mueller wrote:
> On Sunday 07 November 2010 19:20:29 Stefan Schmidt wrote:
> > 
> > > Its time for some house-keeping again. I know many people are working on
> > > patchwork on-going, thanks for that.
> > 
> /patch/2970/ was nak'd / superseded.

Thanks I updated it in patchwork. In the future you can do this by yourself by
adding an account and asking Philip/Crofton to add your account to maintainers.

regards
Stefan Schmidt

Re: Patchwork cleanup weekend in two days

[Tom Rini]

Stefan Schmidt wrote:
> Hello.
> 
> On Thu, 2010-11-04 at 09:27, Stefan Schmidt wrote:
>> Its time for some house-keeping again. I know many people are working on
>> patchwork on-going, thanks for that.
>>
>> Looking throught it during OEDEM did still show up way to many entries. Some are
>> still from 2009. Next Saturday and Sunday I would like to reduce our  current
>> count from 273 patches. 100 or less would be a nice goal imho.
> 
> We are no down to a patch count of 186. With the new patches that came in the
> last two days that makes 100 patches that are gone. Most of them had already
> been applied or superseded by other patches and often were just missing a status
> update.
> 
> For the outstanding patches I see three big groups which need our attention:
> 
> 1) Core/class patches: It would be great if some people more familiar with the
>    core internals of OE could have a look at them and discuss outstanding issues
>    or apply them.
> 
> 2) Stable/2009 patches: We still have patches sitting in patchwork for the
>    stable branch. It would be great if they also could get some attention, not
>    only patches for master.

Would it be possible to get a list of patches that the folks (thanks a 
lot for doing it, everyone!) who did the cleanup felt fit into these areas?

-- 
Tom Rini
Mentor Graphics Corporation

Re: Patchwork cleanup weekend in two days

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07-11-10 19:20, Stefan Schmidt wrote:

> As a side note the patchwork installation will move to our OSUOSL server. The
> new installation will not hold the old patch history we have right now. This
> should be taken as motivation to clean up the rest we have in there. :)

When will the OSUOSL instance start logging patches? If the patch
history is lost, will the userdatabase be moved over?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFM2A7ZMkyGM64RGpERAoQeAJ48BWKEmSiUIZH/ejMxOVKdZjzGVwCeI9ut
AnSlbYl5loOijjjPznrYnHQ=
=IW4l
-----END PGP SIGNATURE-----

Re: Patchwork cleanup weekend in two days

[Philip Balister]

On 11/08/2010 06:53 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07-11-10 19:20, Stefan Schmidt wrote:
>
>> As a side note the patchwork installation will move to our OSUOSL server. The
>> new installation will not hold the old patch history we have right now. This
>> should be taken as motivation to clean up the rest we have in there. :)
>
> When will the OSUOSL instance start logging patches? If the patch
> history is lost, will the userdatabase be moved over?

The user database has more spam accounts than real users.

Philip

Re: Patchwork cleanup weekend in two days

[Stefan Schmidt]

Hello.

On Mon, 2010-11-08 at 17:05, Philip Balister wrote:
> On 11/08/2010 06:53 AM, Koen Kooi wrote:
> >
> >On 07-11-10 19:20, Stefan Schmidt wrote:
> >
> >>As a side note the patchwork installation will move to our OSUOSL server. The
> >>new installation will not hold the old patch history we have right now. This
> >>should be taken as motivation to clean up the rest we have in there. :)
> >
> >When will the OSUOSL instance start logging patches? If the patch
> >history is lost, will the userdatabase be moved over?
> 
> The user database has more spam accounts than real users.

Do we know when the new installation should happen?

regards
Stefan Schmidt

Re: Patchwork cleanup weekend in two days

[Stefan Schmidt]

Hello.

On Mon, 2010-11-08 at 07:25, Tom Rini wrote:
> Stefan Schmidt wrote:
> >
> >On Thu, 2010-11-04 at 09:27, Stefan Schmidt wrote:
> >>Its time for some house-keeping again. I know many people are working on
> >>patchwork on-going, thanks for that.
> >>
> >>Looking throught it during OEDEM did still show up way to many entries. Some are
> >>still from 2009. Next Saturday and Sunday I would like to reduce our  current
> >>count from 273 patches. 100 or less would be a nice goal imho.
> >
> >We are no down to a patch count of 186. With the new patches that came in the
> >last two days that makes 100 patches that are gone. Most of them had already
> >been applied or superseded by other patches and often were just missing a status
> >update.
> >
> >For the outstanding patches I see three big groups which need our attention:
> >
> >1) Core/class patches: It would be great if some people more familiar with the
> >   core internals of OE could have a look at them and discuss outstanding issues
> >   or apply them.
> >
> >2) Stable/2009 patches: We still have patches sitting in patchwork for the
> >   stable branch. It would be great if they also could get some attention, not
> >   only patches for master.
> 
> Would it be possible to get a list of patches that the folks (thanks
> a lot for doing it, everyone!) who did the cleanup felt fit into
> these areas?

Let me try. Stable is easy to identify as it has a stable prefix in the patch.
:)

Stable:
http://patchwork.openembedded.org/patch/2251/
http://patchwork.openembedded.org/patch/2250/
http://patchwork.openembedded.org/patch/2193/
http://patchwork.openembedded.org/patch/1924/
http://patchwork.openembedded.org/patch/1842/
http://patchwork.openembedded.org/patch/1839/

Core:
http://patchwork.openembedded.org/patch/691/
http://patchwork.openembedded.org/patch/972/
http://patchwork.openembedded.org/patch/1067/
http://patchwork.openembedded.org/patch/3446/
http://patchwork.openembedded.org/patch/3427/
http://patchwork.openembedded.org/patch/3428/
http://patchwork.openembedded.org/patch/3406/
http://patchwork.openembedded.org/patch/3382/
http://patchwork.openembedded.org/patch/3235/
http://patchwork.openembedded.org/patch/3201/
http://patchwork.openembedded.org/patch/3196/
http://patchwork.openembedded.org/patch/3139/
http://patchwork.openembedded.org/patch/2933/
http://patchwork.openembedded.org/patch/2592/
http://patchwork.openembedded.org/patch/2563/
http://patchwork.openembedded.org/patch/2558/
http://patchwork.openembedded.org/patch/2555/
http://patchwork.openembedded.org/patch/2526/
http://patchwork.openembedded.org/patch/2248/
http://patchwork.openembedded.org/patch/2200/
http://patchwork.openembedded.org/patch/2171/
http://patchwork.openembedded.org/patch/2491/
http://patchwork.openembedded.org/patch/2487/
http://patchwork.openembedded.org/patch/2094/
http://patchwork.openembedded.org/patch/1978/
http://patchwork.openembedded.org/patch/1926/
http://patchwork.openembedded.org/patch/1907/
http://patchwork.openembedded.org/patch/1858/
http://patchwork.openembedded.org/patch/1828/
http://patchwork.openembedded.org/patch/1741/
http://patchwork.openembedded.org/patch/1631/

I'm pretty sure that I have forgotten some. Many of them have already been
discussed and often the outcome is unclear.

regards
Stefan Schmidt