Sergey Kuleshov:
http://bugzilla.gnome.org/show_bug.cgi?id=525281
http://bugzilla.gnome.org/show_bug.cgi?id=534760
Mine:
http://bugzilla.gnome.org/show_bug.cgi?id=538017
http://bugzilla.gnome.org/show_bug.cgi?id=538019
http://bugzilla.gnome.org/show_bug.cgi?id=532274
Others:
http://bugzilla.gnome.org/show_bug.cgi?id=526492 (note for review by Sandy)
http://bugzilla.gnome.org/show_bug.cgi?id=533033 (discussed but left hanging)
--
-J. Method
Most of the work in 0.1.6 came from non-core developers, so we
couldn't have even had much of a release without you all. I
prioritized releasing over reviewing all outstanding patches. I'm
sorry if you were hurt to find that your patches didn't make it in to
the release, but seeing as how we haven't had a release in three
months I thought it was more important to release ASAP to let people
know we're still alive and to attract more contributors.
> Probably the answer is to deputize more people with commit rights.
Yes, indeed. Finding people who are willing to be thorough about
patch review is not easy, though. It can easily take an hour or more
to review and test even a perfect patch. I would be very glad of your
help in reviewing these.
> Anyway, here's a list of patches on Bugzilla that lack responses:
Thank you for this, it's a very helpful reference. I see no reason
why these can't all be addressed before 0.1.7 is released (hopefully
within a month or so). Especially if I have help doing the reviews.
:-)
Cheers,
Sandy
My point was mainly that it's important to give some little indication
that the patch is acknowledged, even saying, perhaps with a standard
message, "Thanks! Someone will take a look at your patch soon and give
you some feedback on how to improve. Unfortunately, we'll be foregoing
patches until the next release, which will be soon. In the meantime,
you can improve your patch by thinking about possible complications
and writing unit tests to cover them." That is, you'd have a standard
response for an open period and a pre-release period.
Anyway, thanks for responding to my patch. I'll go to work on
addressing your points. No need to carry on this discussion :)
--
-J. Method
My point was mainly that it's important to give some little indication
that the patch is acknowledged, even saying, perhaps with a standard
message, "Thanks! Someone will take a look at your patch soon and give
you some feedback on how to improve. Unfortunately, we'll be foregoing
patches until the next release, which will be soon. In the meantime,
you can improve your patch by thinking about possible complications
and writing unit tests to cover them." That is, you'd have a standard
response for an open period and a pre-release period.
Thank you Andrew, you rock.
Sandy