search

teamneoneko / Avatar-Toolkit

A new modern tool designed to shorten steps needed to import and optimize models into VRChat, Resonite and other similar games.
GNU General Public License v3.0
3 stars 2 forks source link

Deciding on Version Scheme and How we are going to do different blender versions. #3

Open Yusarina opened 2 weeks ago

Yusarina commented 2 weeks ago

I though I add this here so it doesn't get lost in Discord.

We need to decide on how we are going to do versions in the Avatar Toolkit. Currently in Cats we do each version such as 3.6.x.x for Blender 3.6, 4.1.x.x for blender 4.1 and so on. Now this was easy when bl_info was a thing as it allowed us to do this version scheme. But with the new extension system manifest it only allows us to do 3 numbers like 3.6.1.

Now as an example I guess we could do something like 5.0.12, 5.0.15 for blender 5.0 or 5.1.12, 5.1.15 for Blender 5.1.

Also I want to know do we support older version or do we roll on a system that we just support the latest LTS and if older versions break, there break, what do you think?

989onan commented 2 weeks ago

I was thinking that having version numbers like blender's 5.1 would be good, and then hold off new features for new blender versions, to make it so that it matches blender's schema of adding new features with major versions

Yusarina commented 3 days ago

Ok, so we just do 1.0 for the first stable release then 1.1 for a minor release if this is what you mean?

My only issue with this that it's harder to tell which version is for what blender version so we would need to clearly mark it for what version of blender.

What I don't want to try and do is try and support older versions of blender, like Cats was trying to do. We should only support the latest LTS and latest version, like I basically doing for Cats right now. Do you agree?