Tags: yajun-Peng/p4c
Tags
Release 1.2.2.1 (p4lang#3085) The current versioning scheme of the P4 compiler corresponds to the P4 language specification. In particular, the current compiler version corresponds to v1.2.2 of P4_16 Language Specification. This patch updates the P4 compiler version to the following format <major>.<minor>.<patchlevel>.<releasenumber> Where <releasenumber> increments with each release of the compiler. The increment in version number allows to distribute updates for the P4 compiler using package management systems such as DPKG (Debian/Ubuntu) and RPM (Fedora/CentOS). This change was discussed at the P4 open source developer days on November 23, 2021. Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
Enable automatic release on version change (p4lang#2829) * Use version file This commit create a VERSION file that can be used to obtain the current version of P4C. The current version string "1.2.0+g202103291035~a69e52" contains a semantic version, date and current git commit. However, the date makes sense only in packages. Building the same P4C compiler code on a different day should not result in a different version name. The current git commit is automatically from the git history. Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org> * ci: rename 'release' action to 'static-build' This GitHub action doesn't create a release, it only tests if a static build works on Ubuntu 20.04. Thus, using the name "static build" looks more accurately describes what it does. Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org> * Enable automatic releases This GitHub action creates a release in GitHub every time the Version.txt file has been changed. Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>