@@ -17,13 +17,13 @@ server releases. It is organized in the following way:
17
17
* To create a source archive and all supported packages, with a given version:
18
18
19
19
```
20
- make packages PROJECT_VERSION=3.8.1 -rc.1
20
+ make packages PROJECT_VERSION=3.13.0 -rc.3
21
21
```
22
22
23
23
* To create all suported packages from an existing source archive:
24
24
25
25
```
26
- make -C packaging SOURCE_DIST_FILE=/path/to/rabbitmq-server-3.8.1 -rc.1 .tar.xz
26
+ make -C packaging SOURCE_DIST_FILE=/path/to/rabbitmq-server-3.13.0 -rc.3 .tar.xz
27
27
```
28
28
29
29
The standalone package is different because it embeds the build
@@ -35,7 +35,7 @@ build host:
35
35
```
36
36
make package-standalone-macosx
37
37
# or
38
- make -C packaging package-standalone-macosx SOURCE_DIST_FILE=/path/to/rabbitmq-server-3.8.1 -rc.1 .tar.xz
38
+ make -C packaging package-standalone-macosx SOURCE_DIST_FILE=/path/to/rabbitmq-server-3.13.0 -rc.3 .tar.xz
39
39
```
40
40
41
41
The instructions in the [`PKG_LINUX.md`](PKG_LINUX.md) document include a
@@ -57,7 +57,7 @@ based on the last tag and the current HEAD.
57
57
58
58
Here is an example with an explicit version:
59
59
```
60
- make source-dist PROJECT_VERSION=3.8.1 -rc.1
60
+ make source-dist PROJECT_VERSION=3.13.0 -rc.3
61
61
```
62
62
63
63
The version is automatically propagated to the broker and plugins so
@@ -66,7 +66,7 @@ they all advertise the same version.
66
66
The result is then available in the `PACKAGES` subdirectory. You can
67
67
override the output directory with the `PACKAGES_DIR` variable:
68
68
```
69
- make source-dist PROJDCT_VERSION=3.8.1 -rc.1 \
69
+ make source-dist PROJDCT_VERSION=3.13.0 -rc.3 \
70
70
PACKAGES_DIR=/tmp
71
71
```
72
72
@@ -77,7 +77,7 @@ By default, two archives are produced:
77
77
You can ask for more/different types by specifying the
78
78
`SOURCE_DIST_SUFFIXES` variable:
79
79
```
80
- make source-dist PROJECT_VERSION=3.8.1 -rc.1 \
80
+ make source-dist PROJECT_VERSION=3.13.0 -rc.3 \
81
81
SOURCE_DIST_SUFFIXES='tar.xz tar.gz'
82
82
```
83
83
@@ -95,7 +95,7 @@ list of plugins is in the `plugins.mk` file.
95
95
You can override this list by setting the `PLUGINS` variable to the list
96
96
you want:
97
97
```
98
- make source-dist PROJECT_VERSION=3.8.1 -rc.1 \
98
+ make source-dist PROJECT_VERSION=3.13.0 -rc.3 \
99
99
PLUGINS='rabbitmq_shovel rabbitmq_rabbitmq_shovel_management'
100
100
```
101
101
@@ -122,7 +122,7 @@ This has the following rules:
122
122
If you want the source archive to be created automatically, use the
123
123
top-level `Makefile`:
124
124
```
125
- make package-$type PROJECT_VERSION=3.8.1 -rc.1 ...
125
+ make package-$type PROJECT_VERSION=3.13.0 -rc.3 ...
126
126
```
127
127
128
128
Packages are written to `PACKAGES_DIR`, like the source archive.
@@ -146,7 +146,7 @@ with the `VERSION` variable:
146
146
```
147
147
make -C packaging package-generic-unix \
148
148
SOURCE_DIST_FILE=rabbitmq-server.tar.xz \
149
- VERSION=3.8.1 -rc.1
149
+ VERSION=3.13.0 -rc.3
150
150
```
151
151
152
152
### Debian package
@@ -166,18 +166,18 @@ with the `VERSION` variable:
166
166
```
167
167
make -C packaging package-deb \
168
168
SOURCE_DIST_FILE=rabbitmq-server.tar.xz \
169
- VERSION=3.8.1 -rc.1
169
+ VERSION=3.13.0 -rc.3
170
170
```
171
171
172
172
By default, the package version is converted from `VERSION` with
173
- all `-` characters replaced by `~` (eg. `3.8.1 ~rc.1` in the example
173
+ all `-` characters replaced by `~` (eg. `3.13.0 ~rc.1` in the example
174
174
above). If you want to override that conversion, you can specify the
175
175
`DEBIAN_VERSION` variable:
176
176
```
177
177
make -C packaging package-deb \
178
178
SOURCE_DIST_FILE=rabbitmq-server.tar.xz \
179
- VERSION=3.8.1 -rc.1
180
- DEBIAN_VERSION=3.8.1 ~ rc.1
179
+ VERSION=3.13.0 -rc.3
180
+ DEBIAN_VERSION=3.13.0 ~ rc.1
181
181
```
182
182
183
183
### RPM package
@@ -242,12 +242,12 @@ make -C packaging/windows-exe ZIP=/path/to/rabbitmq-server-windows.zip
242
242
243
243
By default, the *product version* is the project version where
244
244
everything following the third integer was replaced by `.0`. Thus it's
245
- only fine if the version is a semver-based version (eg. 3.8.1 -pre.3 or
245
+ only fine if the version is a semver-based version (eg. 3.13.0 -pre.3 or
246
246
3.8.2). If the version doesn't conform to that, you need to set the
247
247
`PRODUCT_VERSION` variable:
248
248
249
249
```
250
- make package-windows PROJECT_VERSION=3.8.1 -rc.1 PRODUCT_VERSION=3.8.1 .0
250
+ make package-windows PROJECT_VERSION=3.13.0 -rc.3 PRODUCT_VERSION=3.13.0 .0
251
251
```
252
252
253
253
To build the Windows package using a Windows machine, follow the
@@ -297,8 +297,8 @@ However, be careful with the versioning! Because all package have
297
297
incompatible requirements, you can only use a version with 3 integers
298
298
(like a final semver-based version):
299
299
```
300
- make packages PROJECT_VERSION=3.8.1
301
- make -C packaging packages SOURCE_DIST_FILE=rabbitmq-server-3.8.1 .tar.xz
300
+ make packages PROJECT_VERSION=3.13.0
301
+ make -C packaging packages SOURCE_DIST_FILE=rabbitmq-server-3.13.0 .tar.xz
302
302
```
303
303
304
304
If you do not follow that rule, the build will fail one way or another;
@@ -309,5 +309,5 @@ Another possibility is to specify the Windows *product version* and
309
309
rely on automatic conversion for Debian and RPM packages (or use the
310
310
`DEBIAN_VERSION` and `RPM_VERSION` variables), but this is untested:
311
311
```
312
- make packages PROJECT_VERSION=3.8.1 -rc.1 PRODUCT_VERSION=3.8.1 .0
312
+ make packages PROJECT_VERSION=3.13.0 -rc.3 PRODUCT_VERSION=3.13.0 .0
313
313
```
0 commit comments