Patch review week
Monday, 8. June 2009, 06:48:35
Michael Scherer just announced this:
Hi fellows packagers,
( and fellow cookers too, by the way )
As announced by Anne some days ago, next week will be devoted to package cleaning. By package cleaning, this mostly mean patchs cleaning, as explained on http://wiki.mandriva.com/en/2010_patchreview
The goal are multiples :
1) be sure that our contributions, when relevant, are integrated upstream, since this ease the maintenance, and also enhance the free software ecology. After all, the sharing of code is the heart of our ideals.
2) be sure that the patchs are still needed, less patch means less problem when updating, less complexity, and less work the next time we do such a week.
3) be sure that patchs are annoted, so we can know why the patch is here, what problem does it solve, etc, etc.
For this event to be sucessful, we need some kind of coordination, and we also would like to be able to count how much packages where cleaned.
So here is what I suggest :
1) use a tag [prw] ( for patch review week, the shorter, the better ) in commit when we cleaned a rpm
2) go in the irc channel #mandriva-commits, and see what packages are currently cleaned,
3) even if I doubt many conflict while arise, it would be good to announce what packages or packages types you are trying to clean. For exemple, games, gnomes, kernel related, etc. Please announce it here, so people can organise them self in small team ( even if this is a team of one
). Priority is to clean main, but you are free to work on contribs too.
4) for each patch, see if it still applies, and if the patch is still needed. If not needed, drop it,
If needed, add a description, the origin of the patch ( ie, upstream, other distribution ), and a possible bug number or url, in the spec file as a comment.
If needed, and relevant for upstream, try to clean it and submit it upstream ( after checking the latest code of course ). Also add that it was sent upstream, how, and possibly with a url.
We do not plan to parse the information or anything, so the format of the entry is free.
Of course, we will not be able to clean everything in one week, even with our super packaging powers. The goal is to start, and to do the cleaning later when it is needed, when we see a package was not cleaned.
And we would also like to make sure that this operation will enhance the karma of the distribution, so do not hesitate to post about it on your blog ( and if you are a packager not syndicated on planet mandriva, just ask the PM team to add your blog ).
So to start, I announce that I plan to clean python, and python modules.
See you tomorow with your broom to clean the svn.
--
Michael Scherer
Hi fellows packagers,
( and fellow cookers too, by the way )
As announced by Anne some days ago, next week will be devoted to package cleaning. By package cleaning, this mostly mean patchs cleaning, as explained on http://wiki.mandriva.com/en/2010_patchreview
The goal are multiples :
1) be sure that our contributions, when relevant, are integrated upstream, since this ease the maintenance, and also enhance the free software ecology. After all, the sharing of code is the heart of our ideals.
2) be sure that the patchs are still needed, less patch means less problem when updating, less complexity, and less work the next time we do such a week.
3) be sure that patchs are annoted, so we can know why the patch is here, what problem does it solve, etc, etc.
For this event to be sucessful, we need some kind of coordination, and we also would like to be able to count how much packages where cleaned.
So here is what I suggest :
1) use a tag [prw] ( for patch review week, the shorter, the better ) in commit when we cleaned a rpm
2) go in the irc channel #mandriva-commits, and see what packages are currently cleaned,
3) even if I doubt many conflict while arise, it would be good to announce what packages or packages types you are trying to clean. For exemple, games, gnomes, kernel related, etc. Please announce it here, so people can organise them self in small team ( even if this is a team of one
). Priority is to clean main, but you are free to work on contribs too.4) for each patch, see if it still applies, and if the patch is still needed. If not needed, drop it,
If needed, add a description, the origin of the patch ( ie, upstream, other distribution ), and a possible bug number or url, in the spec file as a comment.
If needed, and relevant for upstream, try to clean it and submit it upstream ( after checking the latest code of course ). Also add that it was sent upstream, how, and possibly with a url.
We do not plan to parse the information or anything, so the format of the entry is free.
Of course, we will not be able to clean everything in one week, even with our super packaging powers. The goal is to start, and to do the cleaning later when it is needed, when we see a package was not cleaned.
And we would also like to make sure that this operation will enhance the karma of the distribution, so do not hesitate to post about it on your blog ( and if you are a packager not syndicated on planet mandriva, just ask the PM team to add your blog ).
So to start, I announce that I plan to clean python, and python modules.
See you tomorow with your broom to clean the svn.
--
Michael Scherer
WIDGETIZE
How to use Quote function: