On 22 Nov 2018, at 12:48, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
Hi,
Why not following git flow? Keep the development branch for dev and open a 70-release branch to prepare the release. This way, there is no change for most people.
Because our scripts are automated in branch and tag basis. dev-7.0 will generate SNAPSHOT versions for files.pharo.org/70 <http://files.pharo.org/70> and tags (v7.0.0-rc1, for example) will generate a release. We could have another flow, but this was what we decided last week and we will try it (maybe this is wrong and we will need to change it, but well⦠weâll see⦠good part of having a process is that we can iterate on it :P) Esteban
Christophe
Le 22 nov. 2018 à 11:40, Esteban Lorenzano <estebanlm@gmail.com> a écrit :
Hi list,
Well, subject says pretty much all. We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. Then, it will be a âdev-8.0â and so onâ¦
So, be prepared to submit your PRs to dev-7.0 instead development :)
Cheers, Esteban