Re: [BuildStream] BuildStream Versioning & Releases

[Chandan Singh <chandan chandansingh net>]

Hi,

Happy new year all :)

On Thu, Jan 3, 2019 at 1:11 PM Javier Jardón <jjardon gnome org> wrote:
> <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.
>
> while I'm with changes in the release model, bst-1.2.x releases are
> currently being used to build some FOSS projects in the open, like
> freedesktop-sdk and GNOME
>
> Last bst-1.2.x release has been done 3 months ago (5 Oct), and there
> are some fixes in the bst-1.2 branch that those projects are still
> waiting for
>
> So at least I think it would be great to do a another bst-1.2.x
> release before moving to the new release model

There's one more angle to consider here, which is testing of external
plugins. At present, most external plugins resort to testing against
whatever happens to be on master during the test. This is not ideal
for repeatability of those tests. We can work around this by pinning
commit ids, but it would be better if BuildStream tagged development
snapshots more often. Not only will that be useful for early adopters,
but also external plugin maintainers. That way, the plugin maintainers
will not be chasing a moving target while making an update to the
plugins.

This will become more relevant as more plugins move out of BuildStream core.

Cheers,
Chandan