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
"0 patch available" is a good goal to set according to me (like "0 inbox").
On Tue, Sep 11, 2012 at 6:46 PM, Bill Graham <[EMAIL PROTECTED]> 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
> On Tue, Sep 11, 2012 at 8:31 AM, <[EMAIL PROTECTED]> 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
> > 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
> > 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
> > 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