[openstack-dev] Process for proposing patches attached to launchpad bugs?
Robert Collins
robertc at robertcollins.net
Sun Dec 22 08:13:31 UTC 2013
On 22 December 2013 18:02, Chet Burgess <cfb at metacloud.com> wrote:
>
>
> On Dec 20, 2013, at 14:07 , Russell Bryant <rbryant at redhat.com> wrote:
>
>
> It's not your code, so you really can't propose it without them having
> signed the CLA, or propose it as your own.
>
>
> Is there a time limit on this sort of thing? As an example there is a bug we
> opened 2 years ago that still has not been fixed. Someone posted a patch to
> the laundpad 4 months ago that addresses the issue but hasn't submitted a
> review. How long do we wait before its ok to submit the patch so we can have
> the fix? Is there some way we can note where the original code came from so
> as not to be viewed as stealing credit?
>
> I ask now because I planned on posted a review with tests in next week or so
> because we really need the fix
> (https://bugs.launchpad.net/nova/+bug/856764).
There is a time limit - 70 years after the authors death. I suggest
not waiting for that and instead writing a new patch yourself.
-Rob
--
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud
More information about the OpenStack-dev
mailing list