Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 13 Next »

Community Attendees:

Thorsten Lohmar , Rajat Kandoi Barath K, @Hubert Przybyz, steve.vickers @Stefano Brivio, Masaharu Hattori , Tanja de Groot , @Fadime Demirer

Community Attendees:

LF Staff:

Agenda

Antitrust Policy

 

Minutes

Agreement of minutes

  • No comments - approved.

Review of APs

  • Way of working - no feedback, implicit assumption is that it is okay.

Release related discussion

  • M3 (21 Jun), M4 (31 Aug) are key targets

  • Need to complete alpha by M3 and make release candidate available

  • Need to make only changes on the release candidate between M3 and M4

  • At M4 the initial release PR should be ready

  • Sandbox APIs can be released as a sandbox api in the fall 25 meta release, only when becoming stable the API cannot be called sandbox. This is a TSC decision.

  • The API subgroup can manage the alpha and release candidate versions - hence target version can be higher than 0.1.0.

  • Tanja has not seen any use cases where sub projects make alpha releases

  • Can also do a public release w/o a meta release but the trust / quality will be perceived to be lower and risky

Action Items

  • No labels