I forgot to explain that at the end we choose to name our branches “PharoMAJOR.MINOR” instead “dev-MAJOR.MINOR” as proposed at first because that way was not clear what the branches are.
Yes, they are development branches, but they also have the released versions (usually as tags).
After searching some other projects with similar characteristics to ours, we think this was the better approach.
Esteban
> On 5 Dec 2018, at 15:00, Esteban Lorenzano <
[hidden email]> wrote:
>
> Hi,
>
> Working on Pharo7.0 release, I finally changed the default branch.
> “Development" does not exists anymore, now all Pull Requests needs to be done against “Pharo7.0”.
>
> This will allow us to :
>
> - Continue working on Pharo7.0 release
> - Open a Pharo8.0 branch (hopefully next week)
>
> I’m sorry for the mess I can cause to someones, there should not be a problem for most of you but some may need to update their scripts.
>
> Cheers!
> Esteban
Locked
