Well, looking at the list, there are patches that are marked as rejected: those are pretty clear that there is some issue with the patch/patchset.
But seeing a patch row marked as New and for which testbot runs have completed successfully gives no definitive feedback about the actual status. There is no way to differentiate if a patch has been forgotten accidentally, or ignored on purpose (for the benefit of the project) or postponed for later review (in a week or two).
For me personally, in this case, I wouldn't do much with the information since I'm not the author of those patches nor did I help review them. But it would conserve time for both the developers and reviewers if there is a clearer marker of status, instead of guessing it via calendar and/or polling the wine-devel list.
Regards, Indrek Altpere
-----Original Message----- From: Henri Verbeet [mailto:hverbeet@gmail.com] Sent: Wednesday, October 29, 2014 2:42 PM To: Indrek Altpere Cc: Ruslan Kabatsayev; Alex Henrie; Alexandre Julliard; Wine Devel Subject: Re: Need feedback on first four UTF-7 patches
On 29 October 2014 13:21, Indrek Altpere efbiaiinzinz@hotmail.com wrote:
My previous response was mainly to Ruslan's reply, that 30 days waiting time could/should be considered the norm in some cases.
Yeah, it's not.
Perhaps there should be some more clear way to let the developers know that their patches are still not good enough (even to be reviewed and commented on) instead of checking the calendar to guess the status?
The patch status page seems pretty clear to me. Put a different way, suppose you e.g. had additional information about why a patch is still "New", what would you do with that information?