SqueakMap and SqueakSource ought to talk to each other more often

Updating the MQTT4Squeak package reminded me how over-convoluted a job it is to save a package, make a release (on SqueakSource) then make a new release in SqueakMap (in the image) and then finish it off on the SqueakMap website.

It would be a lovely project to make a more integrated process for this. Come on, you know you want to do it...

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: BOZO: Use Multics operating system