Open Stack

> -----Original Message-----
> From: Carl Baldwin [mailto:carl at ecbaldwin.net]
> Sent: Tuesday, November 18, 2014 9:35 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] Stale patches
> 
> +1.  I always hesitate to abandon someone's patch because it is so
> personal.  The auto-expire is impersonal and procedural.  I agree that
> 1 week is too soon.  Give it at least a month.

+1
I am not concentrating on Neutron devs, but I also have the same feeling
on the other area devs. I also cannot abandon the other developers' patches
even if non-activities against some negative feedback.

Thanks
Ken'ichi Ohmichi

---

> Abandoned patches that have some importance shouldn't ever really be
> lost.  They should be linked to bug reports or blueprints to which
> they're related.  So, why do we need to keep them around while there
> is no activity on them?
> 
> Carl
> 
> On Mon, Nov 17, 2014 at 11:45 AM, Collins, Sean
> <Sean_Collins2 at cable.comcast.com> wrote:
> > Perhaps we should re-introduce the auto-expiration of patches, albeit on
> > a very leisurely timeframe. Before, it was like 1 week to expire a
> > patch, which was a bit aggressive. Perhaps we could auto-expire patches
> > that haven't been touched in 4 or 6 weeks, to expire patches that have
> > truly been abandoned by authors?
> >
> > --
> > Sean M. Collins
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev