Hi all,

Allow me to start my reply with a rant. I don't like how the project
is run right now. I think it would be better to invite non-core
contributors and prominent users of buildstream to such meetings. I
understand that it might not be possible if such meetings are held in
person, but it would be nice to at least announce the meeting
beforehand and allow them to weigh in (even if they're not allowed to
vote).

I'll add my comments inline.

Le dim. 9 janv. 2022 à 02:48, Tristan Van Berkom
<[email protected]> a écrit :
> The new milestone overview, which dictates what we expect to land before
> our first candidate release, can be viewed here:
>
>     https://github.com/apache/buildstream/milestone/2

I think buildstream has a lot of rough edges right now to even
consider a release candidate. I would consider this what needs to be
done before a beta release, and then we'll need some serious bug
fixing before a release candidate.

I'd add to the list
https://github.com/apache/buildstream/issues/1263
I think this is potentially (Caching buildtrees only works with BuildElement)

This should definitely be considered as it would affect cache keys:
https://github.com/apache/buildstream/issues/1270

There is also this that we want to either accept or close as wontfix.
https://github.com/apache/buildstream/issues/1384

Then there is a long list of bugs that need to be fixed (a lot of them
are about non-strict mode). These would be fine to leave after the
beta.
https://github.com/apache/buildstream/issues/1304
https://github.com/apache/buildstream/issues/1352
https://github.com/apache/buildstream/issues/1360
https://github.com/apache/buildstream/issues/1394
https://github.com/apache/buildstream/issues/1455
https://github.com/apache/buildstream/issues/1460
https://github.com/apache/buildstream/issues/1461
https://github.com/apache/buildstream/issues/1465


> Meeting minutes
> ===============
>
>  * Walk back over zealous plan to disallow writing in the sandbox

I think this is nice, it allows for some really nice optimizations. It
should probably have an explicit API and a big fat warning about it
though.

> [...]
All the others seem fine.

Regards,

Abderrahim

Reply via email to