Re: [MirageOS-devel] mirageos 3.0 : let's break some APIs

[Richard Mortier <richard.mortier@xxxxxxxxxxxx>]

(Late to the party, sorry...)

On 17 June 2016 at 15:54, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:
> On 05/06/2016 16:47, David Scott wrote:
>> One of the things that puts me off making backwards-compatible changes
>> today is that I fear I might not be able to complete the whole thing in one
>> go and I might leave the world in an inconsistent state which then confuses
>> other people and wastes their time. For example if I changed the `V1.NET`
>> in mirage/types, and then didn't manage to finish updating and releasing
>> everything, and then someone else comes along needing to make an urgent
>> change in `mirage-net-xen` to fix a security issue then they might not spot
>> the problem initially and waste time trying to fix and release master. IIRC
>> when I left big unreleased code changes in ocaml-xenstore people kept
>> tripping over them, assuming they had something in common with the current
>> code in opam.
>
> isn't this a disjoint problem?  If you want to make security fixes to an
> old release, you better create a branch from that release, add the
> change and increase the minor version.  It should be clear that "master"
> or "trunk" are development, leading to next major releases.  Not
> suitable for hotfixes.

I wonder whether we should document practices like this somewhere?
Just so everyone (n00bs included) *is* clear on expectations?

-- 
Richard Mortier
richard.mortier@xxxxxxxxxxxx

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel