This looks nice and useful. I would say that stale patches can be can canceled. The semantics I give to "patch available" is "ready to be committed". So if a reviewer looks at the patch and it does not apply, I think it is fair to remove the patch available state. We should not let this happen too often, otherwise we risk annoying contributors. "0 patch available" is a good goal to set according to me (like "0 inbox").
Cheers, -- Gianmarco On Tue, Sep 11, 2012 at 6:46 PM, Bill Graham <billgra...@gmail.com> wrote: > This is our daily patch available alert, which is now set up. > > Spot checking the list of patch available JIRAs, many have been in this > state for a while. I see some where the developer has been asked to rebase > a patch that no longer applies. In this case should we change these back to > "open" state? > > Also in some cases, it was agreed to wait on a patch until a later date. > Assuming we should leave these as patch available, but that implies that > reducing this list down to size 0 seems unattainable. > > Just curious to hear others thoughts about when to make patches not > available. > > > On Tue, Sep 11, 2012 at 8:31 AM, <j...@apache.org> wrote: > > > Issue Subscription > > Filter: PIG patch available (37 issues) > > > > Subscriber: pigdaily > > > > Key Summary > > PIG-2909 Add a new option for ignoring corrupted files to AvroStorage > > load func > > https://issues.apache.org/jira/browse/PIG-2909 > > PIG-2900 Streaming should provide conf settings in the environment > > https://issues.apache.org/jira/browse/PIG-2900 > > PIG-2879 Pig current releases lack a UDF startsWith.This UDF tests if > a > > given string starts with the specified prefix. > > https://issues.apache.org/jira/browse/PIG-2879 > > PIG-2877 Make SchemaTuple work in foreach (and thus, in loads) > > https://issues.apache.org/jira/browse/PIG-2877 > > PIG-2873 Converting bin/pig shell script to python > > https://issues.apache.org/jira/browse/PIG-2873 > > PIG-2863 Add Map[] support to SchemaTuple > > https://issues.apache.org/jira/browse/PIG-2863 > > PIG-2840 Fix SchemaTuple bugs > > https://issues.apache.org/jira/browse/PIG-2840 > > PIG-2834 MultiStorage requires unused constructor argument > > https://issues.apache.org/jira/browse/PIG-2834 > > PIG-2833 org.apache.pig.pigunit.pig.PigServer does not initialize set > > default log level of pigContext > > https://issues.apache.org/jira/browse/PIG-2833 > > PIG-2824 Pushing checking number of fields into LoadFunc > > https://issues.apache.org/jira/browse/PIG-2824 > > PIG-2816 piggybank.jar not getting created with the current buil.xml > > https://issues.apache.org/jira/browse/PIG-2816 > > PIG-2737 TestIndexedStorage is failing, should be refactored > > https://issues.apache.org/jira/browse/PIG-2737 > > PIG-2712 Pig does not call OutputCommitter.abortJob() on the > underlying > > OutputFormat > > https://issues.apache.org/jira/browse/PIG-2712 > > PIG-2689 JsonStorage fails to find schema when LimitAdjuster runs > > https://issues.apache.org/jira/browse/PIG-2689 > > PIG-2681 TestDriverPig.countStores() does not correctly count the > > number of stores for pig scripts using variables for the alias > > https://issues.apache.org/jira/browse/PIG-2681 > > PIG-2661 Pig uses an extra job for loading data in Pigmix L9 > > https://issues.apache.org/jira/browse/PIG-2661 > > PIG-2657 Print warning if using wrong jython version > > https://issues.apache.org/jira/browse/PIG-2657 > > PIG-2632 Create a SchemaTuple which generates efficient Tuples via > code > > gen > > https://issues.apache.org/jira/browse/PIG-2632 > > PIG-2579 Support for multiple input schemas in AvroStorage > > https://issues.apache.org/jira/browse/PIG-2579 > > PIG-2536 Extend pig to support DISTINCT x.(project) > > https://issues.apache.org/jira/browse/PIG-2536 > > PIG-2495 Using merge JOIN from a HBaseStorage produces an error > > https://issues.apache.org/jira/browse/PIG-2495 > > PIG-2417 Streaming UDFs - allow users to easily write UDFs in > > scripting languages with no JVM implementation. > > https://issues.apache.org/jira/browse/PIG-2417 > > PIG-2362 Rework Ant build.xml to use macrodef instead of antcall > > https://issues.apache.org/jira/browse/PIG-2362 > > PIG-2312 NPE when relation and column share the same name and used in > > Nested Foreach > > https://issues.apache.org/jira/browse/PIG-2312 > > PIG-2277 Make Pig compile against Hadoop 0.22 > > https://issues.apache.org/jira/browse/PIG-2277 > > PIG-2262 AvroStorage dependencies are missing from the release tarball > > https://issues.apache.org/jira/browse/PIG-2262 > > PIG-1942 script UDF (jython) should utilize the intended output schema > > to more directly convert Py objects to Pig objects > > https://issues.apache.org/jira/browse/PIG-1942 > > PIG-1914 Support load/store JSON data in Pig > > https://issues.apache.org/jira/browse/PIG-1914 > > PIG-1777 LoadFunc in a scripting language > > https://issues.apache.org/jira/browse/PIG-1777 > > PIG-1564 add support for multiple filesystems > > https://issues.apache.org/jira/browse/PIG-1564 > > PIG-1549 Provide utility to construct CNF form of predicates > > https://issues.apache.org/jira/browse/PIG-1549 > > PIG-1464 Should clean the Graph when register another Pig Script > > https://issues.apache.org/jira/browse/PIG-1464 > > PIG-1332 NullPointerException in PigServer when invoking debugOff() > > method > > https://issues.apache.org/jira/browse/PIG-1332 > > PIG-1237 Piggybank MutliStorage - specify field to write in output > > https://issues.apache.org/jira/browse/PIG-1237 > > PIG-959 Merge Join fails when there is a blocking operator before it > > in query. > > https://issues.apache.org/jira/browse/PIG-959 > > PIG-483 PERFORMANCE: different strategies for large and small order > bys > > https://issues.apache.org/jira/browse/PIG-483 > > PIG-259 allow store to overwrite existing directroy > > https://issues.apache.org/jira/browse/PIG-259 > > > > You may edit this subscription at: > > > > > https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13225&filterId=12322384 > > > > > > -- > *Note that I'm no longer using my Yahoo! email address. Please email me at > billgra...@gmail.com going forward.* >
