Re: [BuildStream] BuildStream Versioning & Releases

[Tristan Van Berkom <tristan vanberkom codethink co uk>]

Hi,

On Wed, 2019-01-02 at 14:08 +0000, Paul Sherwood wrote:
> On 2019-01-02 13:11, Sander Striker wrote:
> > First of all Happy New Year.
>
> Same to you :-)
>
> <snip>
> > My proposal would be to stop doing 1.x releases altogether, and to
> > wait with doing a 2.0 release until we are satisfied we can give the
> > stability guarantees that are associated with a major release.
> > In the meantime we can figure out a way to do 2.0 alpha releases, or
> > some other convenience for our early adopters.
>
> That makes sense to me, but what about the folks actually cutting code?

To summarize:

  * We should not make a stable 1.4 release or a 2.0 release

  * We should only make 1.3.x developer snapshots

  * We at least need to port bugfixes to 1.2.x and make releases of
    that from time to time, if any bugfixes happen to land on it
    (I presume this to be very low effort).

  * At some undecided day in the future when we think we're really
    ready to be stable, we can make a 2.0 release then.

In general this works for me.

If we went down this road, I would still very much want master to
remain backwards compatible with the 1.2 YAML format... my concern is
that we should be able to test BuildStream master against existing
projects which choose to use 1.2, and not be restricted to only being
usable with projects who have migrated to something new.

If this is impossible for some reason, we should keep a migration guide
up to date and make efforts to make the transition painless.

Cheers,
    -Tristan