search

emil-e / rapidcheck

QuickCheck clone for C++ with the goal of being simple to use with as little boilerplate as possible.
BSD 2-Clause "Simplified" License
998 stars 171 forks source link

Release workflow #227

Open bverhagen opened 5 years ago

bverhagen commented 5 years ago

I am currently working on creating an AUR package (https://aur.archlinux.org/) for Rapidcheck, so it will be available as a package for Arch Linux-based operating systems.

As with most packaging systems, the format relies on a version of the software. I can imagine it would also make life more easy on the users of Rapidcheck when they can name a version. Preferably (and strictly spoken by the PKGBUILD guidelines: https://wiki.archlinux.org/index.php/PKGBUILD#pkgver) this version would match the release version of Rapidcheck.

What are the thoughts of the maintainers and contributors on such a release 'flow'? Are there some additional things that need to be done before or can we just create tags and changelogs on certain points?

To be clear: I am not simply asking to create a release flow, rather I am trying to exchange thoughts with the Rapidcheck community on how to best approach it by me or someone else.

bverhagen commented 5 years ago

The package can be found here: https://aur.archlinux.org/packages/rapidcheck/.

For now I am using version format 'r{nb_of_commit_since_master}.{short_git_hash}', which follows the Arch Linux packaging guidelines (https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function) for packages without tags.

The flow is automated using GitLab. Regularly updating the package to the latest state on master in an automated way is a small next step.