begin quoting Martin Dietze as of Sat, Aug 22, 2009 at 09:08:56PM +0200: > On Sat, August 22, 2009, Carlos R. Mafra wrote: > > > I think that this week I gave up sending those things to the list, > > not because I wanted to be different or not play by the rules, but > > simply because I felt it was not working. > > There have been quite a number of patches posted to this list > which to my knowledge have not made it into the central repo.
Are patches expected to be culled from the list and added automatically, or are they to be posted to the list and tried out by a few folks, and if they work out/don't introduce new bugs, get added to the blessed repository? > There are some bugfixes missing addressing issues more likely > to pop up in daily use (i.e. you don't have to open a 90th > workspace). Actually the debian package in sid has only had > changes related to things like buildability for more than > the last three years. How do you all keep track of 90 workspaces? After a dozen or so, I'm just lost. > I agree that the code quality is quite good and pobably > does not require too much attention, but I nevertheless think > that all those patches should go into a new minor release and > distro users should have a chance to benefit from them. The patches should not be lost, certainly. > If there is anything I could do to help John I'll happily do > it. Maybe we can also distribute responsibility for different > parts of the work (look after the repo, maintain a stable and > a testing branch, review patches etc.)? Just defining a (and I gag writing this) process would be a good start. The website doesn't have anything under the "Coding/Patch Style Guide" (see http://www.windowmaker.info/development.php?show=guide ), which would seem to be the obvious place to start. What should a patch look like? How well should it describe what it does? Where should it be sent? Can you expect an acknowledgement that your patch has been received? Who reviews a patch? Where is it reviewed (e.g., IRC, website, mailing list)? Or do we just dump it into a testing branch and see if anyone finds any bugs? Has all this been hashed out and I'm not not finding it on the webpage? :) -S. -- To unsubscribe, send mail to [email protected].
