I propose to reduce the amount of version we will host here by merging patch version together. So instead of having 3.0.0 and 3.0.1, we should have 3.0, 3.1 and 4.0.
I wonder what the naming should be, we have a branch named 3.0.x on the main repo, maybe we should be consistent and use 3.0.x, but I feel like 3.0 might be a prettier name ?
In this branch based versions, I expect that any changes in the 3.0.x or main branch will be directly reflected on the website, I don't think it is worth waiting to tag a version to push the documentation over to this repository.
We could keep each patch version separate be I wonder what benefit it brings ?
jooola
commented
1 year ago
I propose to reduce the amount of version we will host here by merging patch version together. So instead of having 3.0.0 and 3.0.1, we should have
3.0,3.1and4.0.I wonder what the naming should be, we have a branch named
3.0.xon the main repo, maybe we should be consistent and use3.0.x, but I feel like3.0might be a prettier name ?In this branch based versions, I expect that any changes in the 3.0.x or main branch will be directly reflected on the website, I don't think it is worth waiting to tag a version to push the documentation over to this repository.
We could keep each patch version separate be I wonder what benefit it brings ?
@paddatrapper Any thoughts ?