dev branch?

[ljleb]

Instead of merging PRs directly to main, it could make a smoother transition to merge to an intermediate dev branch so that more people have the chance to test new releases before they are published to the main branch.

This was discussed previously here: #604

[huchenlei]

The problem is how do we incentivise a stable user population to use the dev version of the extension and catch bugs. If we don't have a big enough population actively using the extension, the bug may still not be caught before releasing into main.

I think instead of doing a dev branch, we should offer a way to easily go back to previous "stable version". So that if something breaks in the newest commit, the user always have a fallback. In Chrome, there is a mechanism that if consistent crash is monitored after the push of an update, it will try to fallback to the version before the update.

[ljleb]

Maybe it is possible to use this instead of importlib.reload? https://docs.python.org/3/library/sys.html#sys.modules

[ljleb]

Just to be clear, I don't know if this is a good idea. I'm just suggesting ideas here. I think if a reload of all modules can be done, then the webui host should be responsible for reloading extensions properly.

[lllyasviel]

https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob/59419bd64a1581caccaac04dceb66c1c069a2db1/CHANGELOG.md?plain=1#L28

[ljleb]

This is for 1.4.0 though, which has not yet been merged in main. do you know if it only applies to installing extensions or if it also applies to extension updating?

[catboxanon]

Installing or updating both require a restart so it applies to both.