[Deepsea-users] Backports? Forwardports?

[Tim Serong]

On 02/19/2018 10:43 PM, Nathan Cutler wrote:
>> Say I'm fixing something that's broken in DeepSea 0.8.2 in the SES5
>> branch.  Is the preferred procedure to fix it there (i.e. with a PR
>> against the SES5 branch), then forward-port the fix to master?  Or is it
>> to fix in master, then backport to SES5?
> 
> If you had written Ceph instead of DeepSea, then the answer would surely
> have been "always backport, never forwardport".
> 
> I have been doing it this way in DeepSea as well, and so far nobody has
> objected.
> 
> The advantage of this rule is consistency: you never get any
> cherry-picked commits in master, and all cherry-picked commits in the
> stable branches *must* mention a master SHA1.

Very good point.

Thanks,

Tim
-- 
Tim Serong
Senior Clustering Engineer
SUSE
tserong at suse.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tserong.vcf
Type: text/x-vcard
Size: 4 bytes
Desc: not available
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20180220/3aac3d72/attachment.bin>