For many years, the development of syslog-ng happened on the master branch in Git. However, if you follow that branch, you might have noticed that there has not been much activity on it lately. That is because we introduced a new branch in git called “develop”.
Why? Simply because keeping release code on the master branch and performing actual development on a separate branch makes several internal processes easier.
So, what is the current status? The code for an upcoming bug fix release is already on the master branch. But all other developments are happening in the new develop branch. Most GitHub processes have already been changed to use the new develop branch. This means that:
-
The nightly Debian / Ubuntu packages are generated from the new develop branch: https://www.syslog-ng.com/community/b/blog/posts/nightly-syslog-ng-builds-for-debian-and-ubuntu
-
The nightly syslog-ng container is generated from the above packages: https://www.syslog-ng.com/community/b/blog/posts/nightly-syslog-ng-container-images
-
While not a GitHub action, my weekly unofficial openSUSE / SLES and Fedora / RHEL & compatible packages are now also built from the develop branch: https://www.syslog-ng.com/community/b/blog/posts/rpm-packages-from-syslog-ng-git-head
And what does this mean for developers? It means that from now on, you should prepare your pull requests against the develop branch. The master branch should only contain code merged from the develop branch right before release.
-
If you have questions or comments related to syslog-ng, do not hesitate to contact us. You can reach us by email or even chat with us. For a list of possibilities, check our GitHub page under the “Community” section at https://github.com/syslog-ng/syslog-ng. On Twitter, I am available as @PCzanik, on Mastodon as @Pczanik@fosstodon.org.