[PD-dev] etiquette for closing sourceforge patches?
Hans-Christoph Steiner
hans at eds.org
Mon Jan 2 19:40:29 CET 2006
On Jan 2, 2006, at 2:33 AM, Frank Barknecht wrote:
> Hallo,
> Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
>
>> Personally, I don't think that Miller should close "Rejected" or other
>> patches, only "Accepted". Leaving non-Accepted patches open gives the
>> patch submitter the opportunity to correct problems or update the
>> patch.
>
> With "rejected" patches I meant patches, that were really *rejected*,
> that is, stuff that will never be accepted like e.g. a patch to remove
> all math objects or so. Items, that aren't accepted now, don't have to
> be rejected automatically. However once something really is rejected,
> I don't see, why it should be left in an "open" state.
Yeah I guess that makes sense. Therefore the list will be kept fresh,
without stale abandoned "Rejected" patches staying around. If someone
wanted to revive a rejected patch, they can switch it from Closed to
Open.
.hc
________________________________________________________________________
____
"Information wants to be free."
-Stewart Brand
More information about the Pd-dev
mailing list