Re: [BuildStream] Call for agenda - monthly irc team meeting - Tuesday 14 May

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

On Tue, 2019-05-14 at 13:58 +0100, Sander Striker wrote:
> Hi,
>
> On Tue, May 14, 2019 at 12:08 PM Tristan Van Berkom via buildstream-
> list <buildstream-list gnome org> wrote:
> > On Tue, 2019-05-07 at 11:22 +0100, Tom Pollard via buildstream-list
> > wrote:
> > > Hi, I'm sending out the call for agenda as Laurence is away.
> > >  
> > >  
> > > We have a monthly team meeting on irc coming up next week,
> > details
> > > are:
> > >  
> > > Tuesday 14 May, 14:00 UTC, #buildstream-meetings on GIMPNet.
> > >  
> > >  
> > >  
> > > Do you have anything to add to the below?
> >
> > Yes !
> >
> >
> >  * Potential 1.4 feature release
> >
> >    Abderrahim and I have been discussing the potential of
> > backporting
> >    some features and rolling out a 1.4 release, probably worth a
> > look
> >    over in the meeting.
>
> Why?  I thought we agreed only to do critical patch releases and
> specifically not create additional minor releases beyond 1.2.

I wanted to leave this part to the meeting but it seems you will be
missing it, so:

 * We are seeing various hacks downstream which are working around the
   inability to control `max-jobs` in local builds.

   Some of these include makefiles which patch checkouts of BuildStream
   in CI, others include hacking cmake/ninja in project.conf to make
   jobs unlimited - making WebKit build a bit faster on specific build
   servers which happen to have enough RAM, and crashing all other
   computers horribly.

   So I would next propose adding user configuration for this emergency
   feature addition also in master (and it would probably mean that it
   would only be an observed setting in local execution, as we know
   remote execution will differ).

 * Another motivation is to backport the simpler convenience things
   we've added in BuildStream 2, such as YAML syntaxes related to
   dependency declarations:

   - build-depends
   - runtime-depends
   - ability to refer to cross junction elements with colon notation:
     "junction.bst:element.bst"

 * Another motivation is to provide deprecation warnings in
   BuildStream 1 for the things we know will be different in
   BuildStream 2.

   I.e. it could be useful to support the new CLI syntaxes for the
   commands we are sure about up front, and provide deprecation
   notices (without obsoleting) when running commands which will
   be changed in BuildStream 2.

   Basically a step to hopefully ease adoption of BuildStream 2
   when it eventually comes out.

I am personally less bothered about the last point, (I wouldn't
strongly oppose it if Abderrahim is volunteering to do the work), I
think the second point really doesn't hurt and is nice to have, and the
first point is really a problem right now.

Cheers,
    -Tristan