Re: [Jython-dev] Regarding Pending Patches

[Keshav U. <uk...@no...>]

 It will be good to see the patches are committed soon or if any patch =
needed some improvements it will be good the developer who is reviewing =
the patch suggest improvements as soon as possible ..
It is understood developers are busy with there schedule but believe me if =
patches are getting committed  or reviewed soon it works like a catalyst =
for a contributors to contribute as much as possible .

=20
>>> Philip Jenvey <pj...@gr...> 09/04/07 1:38 PM >>>=20

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 =20
assigned to a developer, they're at least looking at it. You should =20
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 =20
factors: devs have been concentrating on the 2.2 release, and this =20
time of the summer is a common time for folks to take vacation. =20
There's also been a flood of new patch submissions lately (which is =20
great to see).

There's also quite a few older, pending patches that haven't been =20
attended to over the past year because they were aimed for the 2.3 =20
branch, or are CPython > 2.3 functionality. We'll see more action =20
done on those soon now that 2.2 is released.

The IRC channel has been pretty quiet lately, but developers will be =20
in there from time to time; if you think a patch deserves more prompt =20
attention, you might try there, but please be patient =3D]

>>
>> 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 =20
have to run the associated tests, and double check that nothing new =20
has failed in the regrtest. So ensuring your patches are well tested =20
(and don't break the current regrtest) is especially important in =20
getting them accepted quickly.

And of course don't forget to follow the Patch Guidelines on the =20
wiki: http://wiki.python.org/jython/PatchGuidelines

--
Philip Jenvey



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Jython-dev mailing list
Jyt...@li...
https://lists.sourceforge.net/lists/listinfo/jython-dev