David Godin - Hi all. I have a new KIP version ...
Hi all. I have a new KIP version coming. It’s significantly different and I can’t create an upgrade path worth the trouble.
Since user don’t read any release notes or documentation for that matter, what’s the best release approach? Create a new app so both product can live side by side?
4 Replies
Yeah, that’s the best option I can think of. And will allow people to use their existing stuff while working on setting up the new version.
What if we move it under @signalk and deprecate the old one?
We could, but I like my autonomy! How can we make this work?
Your app, your repo, your npm credentials, just under @signalk namespace
But this is no big deal, you can stay 100% independent, just pick a new app name, like @mxtommy/kip3, or pick your own org