Guido Tripaldi

I've just written some new tasks for supporting Distillery 2.1 hot upgrades: **bootleg.build_upgrade** build the app by calling `distillery.release --upgrade`, i.e. producing the `relup` file **bootleg.deploy_upgrade** setup the release for...

Fine, thank you! Maybe it is better I wait for you merge PR #300 to master before I set up the PR, so it will be based on an already...

In the meantime I've upload the `hot_upgrade` branch on github, try to check if it could be ok at https://github.com/guidotripaldi/bootleg/tree/hot_upgrade

I've just submitted the PR #305 adding a hopefully useful sort of mini tutorial for the new tasks. Please let me know about the functional tests :)

Hello @rjanja , thank you! I have rebased the `hot_upgrade` branch and forced a push to origin, now there should be no more conflicts. I've added also the mkdocs documentation,...

no problem, take your time

Hello @rjanja, is there something I can do to help you in the review process for this long pending PR? > Hi @rjanja, @guidotripaldi > > Would you please add...

> hey @guidotripaldi - let me know if you would like to pair on that Hello lessless, Thank you for being available. Unfortunately I have no time at the moment...

Yes it is possible to use Drab broadcast/subscribe functions for triggering updates from other parts of an application, but with some important issues compared to having a native support for...

> > Without PubSub, we have to centralise in the Backend all the calls to every function of all part of your application that needs signaling when data updates, for...