Hi Esteban, you know I'm neither shy on contributing nor doing any work for Pharo but personally I think we open Pharo 8 too early and should better focus our efforts more on finalizing P7 (see below) instead of opening the next construction site.
Things were already shaky and sometimes painful with P7 - nonetheless I managed to get 762 commits into it. Often simple or boring PR's just to get packages, classes, methods in shape and clean up. Funny enough I can now say I'm on top of https://github.com/pharo-project/pharo/graphs/contributors ;) I had a hard time finding out how things work in the new git/pharo/externally managed projects combination - sometimes also with broken or unfinished tools. A newly opened P8 so early adds even more on top... Several things directly came into my mind: 1. http://bugs.pharo.org now points to nirvana now 2. http://ci.pharo.org point to nirvana now as well 3. It's unclear to me what will happen to the bugtracker mailinglist archive. Currently I often use it to stay informed about our changes. Will it stop in december? https://lists.gforge.inria.fr/pipermail/pharo-bugtracker/ 4. The CI for Pharo 7 was not green in most of the latest commits ... and situation for Pharo 8 is not even better now: RED all over on https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/ 5. We still have dirty packages in Pharo 7 - the last remaining issue here https://github.com/pharo-ide/Calypso/issues/386 is still not solved and there was no reaction on Discord after reminding it twice. 6. Calypso still has hard issue in Pharo 7 - most of them already fixed in Calypso project. But integration of the new Calypso version is still pending https://github.com/pharo-project/pharo/pull/2115 Nonetheless we already switch to P8? 7. A change done lately (around 17.12.) was resetting the build numbers - so for whatever strange reason we started with 1 again althoug we were already at Build 1416 for Pharo 7 with all the integrations. https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/ This build number issue was not yet fixed although this is a serious issue to compare image buils or be able to download using Launcher. Nonetheless we already switch to P8? 8. Lately we switched the branches from "development" to "Pharo7.0" and now also "Pharo8.0". This was also just announced - without any discussion in advance forcing people to resetup their tools and local repos. This change is still not event reflected in the contribution guideline ... but we already switch to Pharo 8 9. We still have lots of important and must-fix cases for Pharo 7 https://pharo.fogbugz.com/f/filters/1412/7-0-All 10. There was nothing said about backporting strategy between the new P8 and P7 now... To me it would already help a little bit to clarify the above raised points and get a more detailed info about the next P7 steps towards the release. Independent from that I fear we constantly decouple more and more people with too many process and contribution scheme changes at once. From the discussions on Discord I already see many people struggle - and often not only the beginners. Bye T.
