@julian an other problem just discovered
If I open the chat window and click on the avatar of the chat partner or on my avatar I see a broken link:
@Jenkler "backported" changes behaviour has also changed.
Prior to yesterday, we'd backport changes by cherry-picking them into v1.x.x branch.
From now on, every time a change is important enough that it would've been backported, we will manually release a new patch version (which is how it is supposed to be done).
These are good questions -- I will distill them all into a blog post today or tomorrow.
Remember, before we didn't get to play with major version numbers... it was always 0.x.x. Now we have the option to bump up:
Ok, so -b is for tags ans branches.
I think unofficially, patch versions should not contain upgrade scripts, and so they should be backwards compatible. That said autogenerated builds don't distinguish between them, so it would be difficult to say.
Best advice is to only move forwards, never backwards.
Given some of the opinions in this topic, I'm modifying Misty's behaviour to publish to a weekly release branch instead of the traditionally stable
Sounds good Thanks
@rod I have updated my prod to v1.0.0 tag at the moment. Seems to work fine
Thank you. I will wait for
v1.0.1 and then re-do my DEV environment to test it.
In my DEV currently I did a
git checkout v1.x.x. Once
v1.0.1 is released will I continue to use
v1.x.x or will I specifically reference
You should stick to