Closed mxmehl closed 2 years ago
Just a quick note: I had a similar thought about the tool itself as well. My idea was introducing a dev or next branch and keeping master/main as a stable branch, but still using tags for the versions on it. I think bothe ideas work the same, just with different wording/different perspective. That means I like the idea!
Sure, we could also turn around the wording. I would be fine with both, but for pull requests, master
as the dev branch would be easier.
I would consider this change be more important for the spec as for the tool, but it could still make sense.
Approval by @carmenbianca and @silverhook given in team chat.
Especially if we work on revolutionary features for the spec (like snippets or REUSE.yaml), it would be good to separate the development from a stable branch.
Instead of using a moving tag, which is somewhat hacky, I propose a
stable
branch in which we can backport/cherry-pick translations, FAQ items etc easily.This stable branch can then be the basis for the submodule in reuse-website.