Fitting Blender release cycle

With the new Blender release cycle, between bcon3 and bcon5 (just like right now), taking example of the 2.81 release: https://wiki.blender.org/wiki/Process/Release_Cycle https://developer.blender.org/project/view/88/

In Blender repo - master is future 2.82 - beta of next release, 2.81, is on blender-v2.81-release

Here, I replicated this schema: - master is future 2.82 - blender-v2.81-release is used for fixing bugs only for 2.81

My main concerns is about versionning of the addon. Because version increases in master, when I made a fix in blender-v2.81-release branch, I can't increase the addon version number, because this number is already taken in master. I find quite strange to use the next available number, because it means that this particular version does not include features from version with lower number.

Example: - Addon is in version 1.0.0 - branch blender-v2.81-release is created - a new feature A is added to master, version 1.0.1 - a new feature B is added to master, version 1.0.2 - a fix is added to blender-v2.81-release, how to name it? I don't like 1.0.3, because it doesn't include A and B.

I think, (but it's too late for 2.81 release), that we should manage it this way: - Addon is in version 1.0.0 - branch blender-v2.81-release is created - bump version to 1.1.0 is master, without any other changes - a new feature A is added to master, version 1.1.1 - a new feature B is added to master, version 1.1.2 - a fix is added to blender-v2.81-release, named 1.0.1

Any thoughts?

该提问来源于开源项目:KhronosGroup/glTF-Blender-IO

查看全部
weixin_39975810
weixin_39975810
2020/11/21 17:50
  • 点赞
  • 收藏
  • 回答
    私信

6个回复