Versioning

[DominicD]

Hi @ArthurSonzogni first of all thanks for the great work!

Do you think it would make sense to start Versioning?
I think it would help while using it and also then you can have some release info every time which also helps to know what changed.

[ArthurSonzogni]

Yes, that would be great!

What do you recommend exactly? I mean, I can't make a new version with a changelog too often. So maybe a /dev branch and periodically refresh /main with a new version.
The only drawback is this would delay new features by a couple of weeks for the people using /dev

Do you have anything to recommend?

[DominicD]

Well I do not have any experience with this myself. However I would suggest having a look at how it is handled in other popular open source projects and think about what style works for you.
Would be great if other user could say what they want as well. Maybe it would make sense to ask the maintainers of the projects using ftxui you linked.

I think Semantic Versioning makes sense and choosing on of the workflows (example post).
There is also a lot of great tooling around these e.g. gitversion.

Maybe you already have some experience with it?

[ezzieyguywuf]

I don't currently use ftxui, though I've had my eye on it for a while

Adding releases (ie releasing a version) is a great idea, as it allows package maintainers for various OSes to create a package for your release.

Regarding the actual scheme to use: SemVer is widely used and recognized. v1.0.0 is typically considered a significant initial release. Many open source projects defer v1.0.0 until they've been "out in the wild" for a while and things have stabilized - some never make it there lol.

Releasing versions doesn't have to be a big headache. I encourage you to do so with as little effort as possible and then scale as (or if) needed.

[DominicD]

Thank you for creating a first release and the extensive changelog!
One more suggestion I have now that I see it, is to actually use the Github Release feature.
If you use it it creates the tag and also gives a nicer view. Here you can see an explanation: releases vs tags

Of course its up to you if you care about it. I am happy anyway 👍

[ArthurSonzogni]

Github release is now automatically used whenever I push a new tag. Moreover, artefact are automatically created (Deb, RPM, etc...).

@DominicD, would you have more suggestions after that?

[DominicD]

Perfect. Only suggestion is keep up the great work :)

[BurningEnlightenment]

@ArthurSonzogni it's been a while since 3.0.0 has been released, are there any plans for "officially" releasing the current changes?

[ArthurSonzogni]

I feel the need to switch version.
There is still one more breaking change I would like to add:
https://github.com/ArthurSonzogni/FTXUI/tree/textarea

After that, it shouldn't take too long.

[BurningEnlightenment]

That's hot stuff, thanks!
Also, it would be nice if critical/major bug fixes like #421 were "backported" and packaged as early/seperate patch releases.

[ArthurSonzogni]

I ended up releasing v4.0.0 earlier. Mainly because of the clang bug affecting v3.0.0.