Hi Jean, As every year, we try to release in april. Now if this will be there or not, it always depends on several things, but for now we are pretty confident on it :P About renaming branches... we will not do that for the moment, sorry. We have discussed a lot in the past and this naming pattern is working so far. But as every release also, we will re-discuss our process after the release happens, to iterate on it and improve... what would be the rational behind having a main branch as default instead a branch with the version we are working on? (I could consider start having branchs named, e.g. pharo12-dev, to differentiate it from the stable branch, but since that would mean to change a lot of tools that depend on the naming, it has to be considered careful).
cheers! Esteban On Mar 10 2023, at 1:42 pm, Privat, Jean <privat.j...@uqam.ca> wrote: > Nice, > > do you have a timeframe in mind for the release, or this will be "when it's > ready"? > Also, a suggestion: do not create a `Pharo12` branch yet but use a > master/main one (and make it the default branch). > It helps newcomers to understand more easily the structure of the project. > > -J > ________________________________________ > De : Esteban Lorenzano <esteba...@netc.eu> > Envoyé : 10 mars 2023 05:03 > À : Pharo Development List > Objet : [Pharo-dev] [ANN] preparing for release, freezing enhancements :) > > Hello, > We are slowly preparing to release Pharo 11. > For those making changes that are not bugfixes, we will open Pharo 12 branch > beginning of next week. > > Please, stop submitting enhancement/modification changes to Pharo 11, but > instead all bugfixes you can contribute are welcome :) > cheers! > Esteban >
