From: Philip J. <pj...@gr...> - 2007-09-04 08:08:45
|
On Sep 4, 2007, at 12:32 AM, dperez wrote: > > And how can I know if a patch has been accepted or not? > If I see some accepted patch, I'm more encouraged to post more. > When someone says so on the patch issue, or if you see it become assigned to a developer, they're at least looking at it. You should get an email when anything changes on your patch issue. > > Mehendran T wrote: >> >> Hi, >> >> Please clear my doubt.... >> >> I found that many patches are pending. >> Won't it be a problem while applying them? >> >> It is because they might have been taken from >> different versions and there may be conflict in >> files. I am curious as to know what can be the >> solution to get them in place. I think there's been a lag in response to patches lately due a couple factors: devs have been concentrating on the 2.2 release, and this time of the summer is a common time for folks to take vacation. There's also been a flood of new patch submissions lately (which is great to see). There's also quite a few older, pending patches that haven't been attended to over the past year because they were aimed for the 2.3 branch, or are CPython > 2.3 functionality. We'll see more action done on those soon now that 2.2 is released. The IRC channel has been pretty quiet lately, but developers will be in there from time to time; if you think a patch deserves more prompt attention, you might try there, but please be patient =] >> >> And also, Is it taking time due to the above >> difficulty in commit work? >> After reviewing and applying the patch, the developer is going to have to run the associated tests, and double check that nothing new has failed in the regrtest. So ensuring your patches are well tested (and don't break the current regrtest) is especially important in getting them accepted quickly. And of course don't forget to follow the Patch Guidelines on the wiki: http://wiki.python.org/jython/PatchGuidelines -- Philip Jenvey |