Hi,
https://git.fsfe.org/reuse/docs/src/branch/main/CHANGELOG.md has 3.1 - 2023-06-21 and there is https://github.com/fsfe/reuse-docs/pull/133 to prepare 3.2 of the spec
_but_ https://reuse.software/spec/ has Version 3.0 and https://github.com/fsfe/reuse-docs/tags latest tag is 3.0
which confuses me.
So is version 3.1 of the specification released and the website and git tag should be fixed to reflect this?
Best, Bernhard
Hi Bernhard,
Version 3.1 is yanked. The referenced PR fixes up the change log to correctly spell this out.
After PR 133 is merged, I want to move some things around to be less confusing. At present, `main` is the default branch, but `stable` is the one that is live. This is confusing, and I want to change that. But it's easier to make such changes after the big PR 133 is merged.
Yours with kindness, Carmen
Le mardi 30 avril 2024 à 15:31 +0200, Bernhard Reiter a écrit :
Hi,
https://git.fsfe.org/reuse/docs/src/branch/main/CHANGELOG.md has 3.1 - 2023-06-21 and there is https://github.com/fsfe/reuse-docs/pull/133 to prepare 3.2 of the spec
_but_ https://reuse.software/spec/ has Version 3.0 and https://github.com/fsfe/reuse-docs/tags latest tag is 3.0
which confuses me.
So is version 3.1 of the specification released and the website and git tag should be fixed to reflect this?
Best, Bernhard
REUSE mailing list REUSE@lists.fsfe.org https://lists.fsfe.org/mailman/listinfo/reuse
This mailing list is covered by the FSFE's Code of Conduct. All participants are kindly asked to be excellent to each other: https://fsfe.org/about/codeofconduct
Hi Carmen,
Am Dienstag 30 April 2024 20:20:37 schrieb Carmen Bianca BAKKER:
Version 3.1 is yanked.
good to know, thanks for the clarification!
The referenced PR fixes up the change log to correctly spell this out.
Which one? To me https://github.com/fsfe/reuse-docs/blob/main/CHANGELOG.md (main) still has it. (stable) does not, but I'd recommend add a note instead of just removing the 3.1 info, something like 3.1 (cancelled, not going to be relased) at least for the time being.
Best Regards, Bernhard
Hi Bernhard,
Le jeudi 02 mai 2024 à 09:09 +0200, Bernhard Reiter a écrit :
Which one? To me https://github.com/fsfe/reuse-docs/blob/main/CHANGELOG.md (main) still has it. (stable) does not, but I'd recommend add a note instead of just removing the 3.1 info, something like 3.1 (cancelled, not going to be relased) at least for the time being.
Yes, that is what will be done:
https://github.com/fsfe/reuse-docs/pull/133/files#diff-06572a96a58dc510037d5...
Yours with kindness, Carmen
Hello,
which confuses me.
I think it would help if the maintainers do describe their branching model somewhere.
Additionally I would suggest to have look at the OneFlow branching model. I am assuming that this repo is good fit for it.
https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow
Best, Christian Buhtz
Hi Christian,
Le mercredi 01 mai 2024 à 09:26 +0000, c.buhtz@posteo.jp a écrit :
I think it would help if the maintainers do describe their branching model somewhere.
I will indeed do this soon. This thread is a good reminder that it's an important thing to be doing.
Additionally I would suggest to have look at the OneFlow branching model. I am assuming that this repo is good fit for it.
https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow
Thanks for this article! It was a good read. Incidentally this model is already used for the tool, but it's not especially handy for the website + documentation, unless the release branch can be (somewhat) long-lived.
Yours with kindness, Carmen
Hello Carmen,
Am 01.05.2024 12:48 schrieb Carmen Bianca BAKKER:
already used for the tool, but it's not especially handy for the website + documentation, unless the release branch can be (somewhat) long-lived.
Depending on the documentation system most of the are able to select code from a repo based on a tag not only on a branch. One branch is enough. No need for more. ;)
Kind Christian
which confuses me.
I think it would help if the maintainers do describe their branching model somewhere.
Absolutely, and the repository does exactly that ;)
https://github.com/fsfe/reuse-docs/#branches
Best, Max
-- Max Mehl Open Source Strategy & Governance Enterprise-Team Chief Technology Office (CTO), TO.IP E-T-378
DB Systel GmbH Bahnhofplatz 1b, 76137 Karlsruhe
________________________________
Pflichtangaben anzeigenhttps://www.deutschebahn.com/pflichtangaben/20240501
Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier: https://www.deutschebahn.com/de/konzern/datenschutz