Tagging releases? Useful or not?

Before the creation of open-release/xxx.1, we will have to run our tests on the master branch, and we will no longer create alpha tags. This is what we agreed on in the BTR meeting, right?

Yes, me neither, which is why I’d like to keep having tags, and manually apply security patches on top of the tag that I work on.

Well, sort of. A two-month cadence would give us three tags, which would be consistent with what we have right now. Also, I’d be willing to bet that sometimes one month goes by without modification to the release master branch, whereas this does not happen over two month periods.

I’m not saying either that two months is the best cadence… Less frequent tags would be too infrequent to my taste, but I don’t have anything against more frequent tags.

Security fixes would immediately go to the release master branch, which is the one that is installed with the native installation, but they would only get tagged every two months. People working with tags would have to manually pull the security patches.

1 Like