I just branched off this discussion from the Proposal: Make style ids immutable thread, since it seemed to go rather off-topic. (per https://community.smartthings.com/t/how-to-split-topics-using-discourse-forum/10687/6, this feature is rather hidden, but it’s the admin wrench icon in the right-hand column)
I think we should just branch off a “1.0.1” branch once we’re ready to start accepting 1.0.2 styles in the repo.
One thing I think we should consider is getting rid of “master” and just always work in the (current) version branch. That way consumers of our styles never have to worry about us transitioning between versions in a given branch (i.e. “master”), and they can just hop to a newer CSL version at their leisure.
I don’t think we should try to keep 1.0.1 and 1.0.2 branches synced with style updates (to the extent that those can be transferred between CSL versions), which seems like a very annoying task. For the jump from 1.0 to 1.0.1, we basically just froze “1.0” and only received and accepted pull requests to the (then 1.0.1) “master” branch. I recommend doing the same here again.
We might also want a freeze period between finalizing the 1.0.2 schema/spec and starting to accept 1.0.2 styles in the repo, to give the major CSL processors and software clients some time to catch up and prepare for the new release.