��The fact that Athens are part of Pharo distribution don't means, that its repository should be abandoned and all updates should come directly to Pharo. That would be a huge mistake.
That's how I've done it recently.
I'll merge the changes from pharo -> athens repository.
��Doing everything in a monolithic image is a planning mess, and works fine only for bug fixing or small refactorings.
Anything which requires sizable planning and designing, should have own line of development and maintenance,
like that there's a clear separation of the responsibility for maintaining the project in healthy state and less bottlenecks.
no idea��� I guess is the same case, but I have no control over that area.��Igor will know better :)
Esteban
--
Best regards,
Igor Stasenko.