Hi, I have created maintenance branch release/4.0, branched off of the current master.
This means the master branch is being frozen for major and breaking changes, until 4.0 is released. In practice, it means every git push origin master is followed by the sequence git checkout release/4.0 git merge -ff-only master git push origin release/4.0 to keep everything in sync, until SOCI 4.0.0 is out (soon!). The main purpose of the early branching is to test CI-based deployment of website and documentation: 1. CircleCI for master builds the documentation, uploads the documentation as well as uploads the HTML files of the website 2. CircleCI for release/X.Y builds the documentation for release/X.Y and uploads the documentation only This keeps the whole website and versioned continuously and automatically updated on pushes to master or release/X.Y branches. See http://soci.sourceforge.net/doc.html All details documented in the RELEASING.md file. Any feedback welcome. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ soci-devel mailing list soci-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-devel
