Release policy

[VaiTon]

At the moment, we release to iOS and Android internal testing branch whenever there is a commit on a branch which follows the template release/....

I'd like to automate at least the release to the internal branch of each platform app store so that developers and team members can test changes whenever they are approved and merged.

There are two main options:

1. Release every day at a certain time (nigthly ofc) from develop
2. Release at every commit to develop

I'd also suggest that we release to closed beta whenever there is a push to a release/... branch, like we did before.

Any opinion is appreciated!

cc @g123k @monsieurtanuki @teolemon @stephanegigandet @openfoodfacts/openfoodfacts-flutter

[monsieurtanuki]

I can't be helpful for this part of the project: no particularly good ideas, not able to implement them either.
cc. @M123-dev

[M123-dev]

Heyy @VaiTon sorry for the late reply.

I've had some talks about this with @teolemon already, his opinion was that he would prefer to have manual control over the releases at least at that time.
That was the reason why we removed release-please. I just saw your PR and I think a regular release to the internal is good. For the public thats another story. But the final decision has pierre.

[VaiTon]

No problem and thank you for your reply! I'm ok with that. Automate releasing to internal makes sure that changes can be tested quickly even by who doesn't have flutter setupped.