Tooling to ease creating releases
Project description
This project contains tooling and templates to ease creating releases on GitHub and publishing them on PyPI. Designed to be used by Robot Framework and tools and libraries in its ecosystem, but can naturally be used also by other projects.
To be able to take this project into use, you should know at least basics of Python packaging.
Main features
Utilities that can be used by custom Invoke tasks. These utilities are importable directly from the rellu module:
Setting project version, including automatically setting it to the next suitable development version.
Setting common labels in the issue tracker.
Generating release notes based on issues in the tracker. Requires project to use pre-defined labels.
Generic Invoke tasks in the rellu.tasks module:
Cleaning temporary files and directories.
tasks.py file implementing Invoke tasks using the aforementioned utilities. Other projects can use it as an example or template.
Step-by-step instructions for creating releases in BUILD.rst file using Invoke tasks defined in the tasks.py file, git, and other tools. Also this file can be used as a template.
setup.py using general good practices that can also be used as a template. There’s also super simple MANIFEST.in, but this project doesn’t need setup.cfg.
Dependencies
Rellu is designed to be used together with Invoke which is also used internally. All project dependencies are listed in the requirements.txt and requirements-build.txt files.
Rellu itself works only with Python 3.6 or never, but projects it is used with can naturally support also older Python releases. Rellu is developed and tested on Linux, but ought to work just fine also on OSX. Using it on Windows may work, but that’s not tested or supported.
Required project setup
To be able to generate release notes automatically, issue trackers must be configured using these rules:
Milestones must match project versions and use format v1.2 or v1.2.1.
Labels must be configured using the provided utility.
Milestones and labels must be used consistently:
Valid issues must have type defined as a label bug, enhancement or task. Issues with the task type are not included in release notes.
Issues should have priority set. See various prio- labels.
Issues belonging to a certain milestone should have that milestone set.
Issues included into a certain preview releases should have a matching label set (e.g. a1, b2, rc3).
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
