Hi everyone, Last week I did these tasks: - Fix PR #9423 RB - Fix extract method refactoring issue <https://github.com/pharo-project/pharo/pull/9423> . Check these changes in the PR #9492 <https://github.com/pharo-project/pharo/pull/9492> - Fix PR #9442 RB - Add push down methods transformation command <https://github.com/pharo-project/pharo/pull/9442> - Migrate *RBChildrenToSiblingsRefactoring* to refactoring 2 - Migrate variable commands to use Transformations of refactoring2 - Do a baseline of migration: document <https://docs.google.com/document/d/1RsILFmKoU9gmgOTWNVajMo1xC3YBLnBd0V3vk0JAkMc/edit?usp=sharing> - Introduction - Steps to migrate - Migration of commands - Pros and cons - Example of migration Tasks for this week: <https://github.com/pharo-project/pharo/issues/9142> - Start to migrate (if the migration is approved) - Improve messages: No understable message #9229 <https://github.com/pharo-project/pharo/issues/9241> - Fix issue: push up refactoring could ask and DO it when the user want <https://github.com/pharo-project/pharo/issues/9421>s Regards, Evelyn C.

> Hi everyone, > > Last week I did these tasks: > > - Fix PR #9423 RB - Fix extract method refactoring issue <https://github.com/pharo-project/pharo/pull/9423> . Check these changes in the PR #9492 <https://github.com/pharo-project/pharo/pull/9492> > - Fix PR #9442 RB - Add push down methods transformation command <https://github.com/pharo-project/pharo/pull/9442> > - Migrate RBChildrenToSiblingsRefactoring to refactoring 2 > - Migrate variable commands to use Transformations of refactoring2 > - Do a baseline of migration: document <https://docs.google.com/document/d/1RsILFmKoU9gmgOTWNVajMo1xC3YBLnBd0V3vk0JAkMc/edit?usp=sharing> > - Introduction > - Steps to migrate > - Migration of commands > - Pros and cons > - Example of migration > > Tasks for this week: > <https://github.com/pharo-project/pharo/issues/9142> > > - Start to migrate (if the migration is approved) Evelyn what would be great is to see if we can parametrized the tests of Refactoring to execute for both RB and RB2. > - Improve messages: No understable message #9229 <https://github.com/pharo-project/pharo/issues/9241> > - Fix issue: push up refactoring could ask and DO it when the user want <https://github.com/pharo-project/pharo/issues/9421>s > > Regards, > > Evelyn C.

Hi Stef, Yes, yesterday I checked how to use parametrized tests in Pharo, and I use this to test the migrated refactorings, after migrating all, I will add parametrized tests to all refactorings and transformations. Best regards, Evelyn Cusi El mar, 22 jun 2021 a las 13:18, stephane ducasse (< stephane.ducasse@inria.fr>) escribió: > Hi everyone, > > Last week I did these tasks: > > - Fix PR #9423 RB - Fix extract method refactoring issue > <https://github.com/pharo-project/pharo/pull/9423> . Check these changes > in the PR #9492 <https://github.com/pharo-project/pharo/pull/9492> > - Fix PR #9442 RB - Add push down methods transformation command > <https://github.com/pharo-project/pharo/pull/9442> > - Migrate *RBChildrenToSiblingsRefactoring* to refactoring 2 > - Migrate variable commands to use Transformations of refactoring2 > - Do a baseline of migration: document > <https://docs.google.com/document/d/1RsILFmKoU9gmgOTWNVajMo1xC3YBLnBd0V3vk0JAkMc/edit?usp=sharing> > - Introduction > - Steps to migrate > - Migration of commands > - Pros and cons > - Example of migration > > Tasks for this week: > <https://github.com/pharo-project/pharo/issues/9142> > > - Start to migrate (if the migration is approved) > > > Evelyn what would be great is to see if we can parametrized the tests of > Refactoring to execute for both RB and RB2. > > - Improve messages: No understable message #9229 > <https://github.com/pharo-project/pharo/issues/9241> > - Fix issue: push up refactoring could ask and DO it when the user want > <https://github.com/pharo-project/pharo/issues/9421>s > > Regards, > > Evelyn C. > >