ffbe5b449d
Summary: With this diff, each build of Memgraph has a version that uniquely identifies it. The given version uniquely identifies both official release builds and development builds. Enterprise/community builds are also differentiated in the version. Also, support for custom suffixes is added to support custom builds for customers. Reviewers: teon.banek Reviewed By: teon.banek Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D2662
44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
# Memgraph Release Packaging
|
|
|
|
Various tools and packaging configuration files should be put under this
|
|
directory. Common files for all packages can be kept in the root of this
|
|
directory, for example `memgraph.service`. If the common stuff should be
|
|
grouped, it should be in a subdirectory. `examples` directory is one such
|
|
case. Packaging specific stuff must have its own directory.
|
|
|
|
Currently we support distributing Memgraph binary through the following
|
|
packages.
|
|
|
|
* Debian package
|
|
* RPM package
|
|
* Docker image
|
|
* ArchLinux package
|
|
|
|
## Release process
|
|
|
|
While releasing an official version of Memgraph, there are two possible
|
|
scenarios:
|
|
* First release in new major.minor series
|
|
* Patch release in existing major.minor series
|
|
|
|
To release a new major.minor release of Memgraph you should execute the
|
|
following steps:
|
|
1. Land all diffs that must be in the new release
|
|
2. Document all changes in `CHANGELOG.md` and land them
|
|
3. From the `master` branch, create a branch named `release/X.Y` and push it
|
|
to `origin`
|
|
4. Create the release packages triggering a `mg-master-release-branch-test`
|
|
using branch `release/X.Y` on Apollo
|
|
5. Enjoy
|
|
|
|
To release a new patch release in an existing major.minor series you should
|
|
execute the following steps:
|
|
1. Checkout to the `release/X.Y` branch
|
|
2. Cherry-pick all landed commits that should be included in the patch version
|
|
3. Document all changes in `CHANGELOG.md` and commit them
|
|
4. Edit the root `CMakeLists.txt` and set `MEMGRAPH_OVERRIDE_VERSION` to
|
|
`X.Y.patch` and commit the change
|
|
5. Create the release packages triggering a `mg-master-release-branch-test`
|
|
using branch `release/X.Y` on Apollo
|
|
6. Enjoy
|