Feature Freeze on Monday !

[teolemon]

• We start the Feature Freeze period on Monday. No new features are allowed to be merged during this period. Only bug fixes related to the features developed during the development phase can be merged.
• For the next cycles, in general, I'd like a feature freeze on Mondays, with a Release Candidate the same day, so that we can have a midweek release, and hopefully a peaceful Friday. If we're not happy by the Weekly Call (on Thursdays), we postpone the release on next Monday, or until we can ship confidently (with the exception of Fridays)

@M123-dev @g123k @monsieurtanuki

[monsieurtanuki]

• A release a week seems a bit too frequent. It looks like we would spend more time releasing or waiting for the release to be confirmed, than to actually fix bugs and add features. First and third Monday of the month instead?
• I don't mind if I don't merge myself and let an admin (with a clearer view) do it.
• It's still not very clear what should be done and when. OK the feature freeze periods start on Monday - do they end after a confirmation at the weekly call?
• What about setting priorities (with labels) more systematically? We would focus on what is more important for the app.

[g123k]

• For the cycle of a release, we have not chosen a duration (at least for now). So, we will stay as today, that is to say "when it's ready". The more important here is that we want:

  • To ensure that we never release at the end of a week
  • We have enough time for a public beta

• For the "release freeze" process, this is how it will work:

  • On a Monday, we won't merge any PR with new features (but they can be approved)
  • Only fixing bugs can be approved AND merged
  • We will have 1 or 2 days to do a public beta (or more if necessary)
  • If there is no particular bug, at the end of the beta, we will release the version
  • And at this time, we will start the development cycle, where pending PRs will be merged
  • During the beta, on our side, we will work on a shared manual testing process that each release should tick.

• As you mentioned, the idea would be that every new development period should have priorities
  Clearly, we won't do it well the first time, but the idea is to improve step by step.