Milestones

List view

• BuildStream 2.0 stable blockers

  This milestone is intended to record sensible blockers to an actual 2.0 stable release of BuildStream.

  No due date

  •12/12 issues closed
  100% complete0 open12 closed

• BuildStream 2.0 API Freeze

  This milestone represents issues which need to be solved in order to reach an establish stable API for BuildStream 2.0. After completing these tasks it will be a good time to release an initial BuildStream 2.0 beta release and start focusing on fixing issues leading up to an actual 2.0 stable.

  No due date

  •29/29 issues closed
  100% complete0 open29 closed

• Immediate Priorities

  Opening this milestone to capture the items which we have agreed should land sooner rather than later. In order of priority: [1) Expire artifacts on artifact share servers](https://gitlab.com/BuildStream/buildstream/issues/136) A stop gap solution to this will suffice to begin with, to solve the problems currently seen by other projects. We could then close this one out and then raise another issue in order to capture the complete solution. [2) Expire artifacts in local cache](https://gitlab.com/BuildStream/buildstream/issues/135) This has been spoken about f2f a bit already, implementation plan needs to be publicly written up. [3) Performance issues with running the artifact cache](https://gitlab.com/BuildStream/buildstream/issues/189) This is a real issue for anyone wanting to deploy built artifacts. [4) Event Hooks: Trigger external commands on certain events](https://gitlab.com/BuildStream/buildstream/issues/188) Previous proposal will need some adjustments to accommodate Bazel Build Event Protocol. [5) Storing Source references separately: ie, do not automatically update git checkout with refs](https://gitlab.com/BuildStream/buildstream/issues/248) [6) Print summary of failed modules when there is a build failure](https://gitlab.com/BuildStream/buildstream/issues/247)

  No due date
  0% complete0 open0 closed