pharo
pharo copied to clipboard
TaskIt should be resynced for Pharo12
Martin started to integrate some fixes in pharo-contribution and the Pharo90 should benefit from this.
This issue has either a default title or empty body. We would appreciate it if you could provide more information. Note: I am not a very intelligent bot, I can only react to new comments. Please add a comment for me if you update the body or title.
While doing this be aware of https://github.com/pharo-contributions/taskit/issues/93
Hello, I released Taskit v1.2.0 where:
- I pushed all contributions in Pharo 10 (and some time ago I did the same for Pharo 9) (I hope I didn't miss anything... I'm quite sure I didn't)
- Includes changes on Taskit repo's master from almost 2 years (see tag description for details).
Doe we need to merge something in Pharo or can this issue now be closed?
I think the original intention of the issue was to upgrade Pharo so it loads the new version of Taskit.
So, IIUC, it should be closed when a PR upgrading to v1.2.0.
I see the project is referenced in BaselineOfBaseLibraries>>#baseline: with:
spec baseline: 'TaskIt' with: [
spec
loads: #('coreTests');
repository: repository ].
Should we convert it to external project like Iceberg and others?
Do we sync before P11 release or after?
I guess this week I can re-commit new changes in P11 to TasKit repo, and then commit to this repo's Pharo11 branch. Do you know who to ask for the possibility to make the repo external like Iceberg and others? On the Taskit's repo, there wasn't any new commit (on master branch) since my previous commit, April/2022.
EDIT: or are you going to do it already, @jecisc ? be welcome :)
It's not on my todo (yet) ahah
I was wondering because I see it tagged for Pharo 11 but the feature freeze started. I don't follow the changes of this project but if they are new features or refactoring we should wait P12. If they are bug fixes, then we should do the sync :)
move the milestone, please