[Rdo-list] OPM downstream patches

[Emilien Macchi]

On 01/18/2016 08:56 AM, Ivan Chavero wrote:
> 
>> I can only assume that consumers and users of RDO do not expect
>> midstream patches in their packages.
>> We don't ship anything custom for Nova, Cinder, etc - OPM shouldn't be
>> any different.
> 
> You have a point here, the problem is that sometimes reviews take a lot of
> time to be accepted and there are bugs that have to be solved really fast.

What? Are you saying Puppet OpenStack patches take time to be merged?
You can ask to the contributors, if your patch is passing CI, I'm sure
it's landed in the same day or the next 2 days maximum.
By the way, we have a weekly meeting where we do bug and review triage.
If you have any patch that needs attention, please come-up and we'll
help it to make it.

So please, don't say it takes time to merge Puppet patches upstream.

> That's why with some exceptions there are a lot of patches into OPM's
> patches repo, this patches stay there until the upstream patch is accepted.
> In RDO there should be constant rebases since there's no code freeze
> like in OSP so patches that are alreay in upstream are deleted more often.
> 
>>From my point of view whe sould not have any fork of the puppet modules,
> we should be using the upstream release of the module and add patches when needed.
> 
> 
> Cheers,
> Ivan
> 
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
> 
> To unsubscribe: rdo-list-unsubscribe at redhat.com
> 

-- 
Emilien Macchi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160118/38df57fb/attachment.sig>