1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
|
# Releasing
## Source code
In `check_pgactivity`:
* edit variable `$VERSION`
* update the version and release date at the end of the inline documentation
* date format: `LC_TIME=C date +"%a %b %d %Y"`
In `check_pgactivity.spec` (RPM file):
* update the tag in the `_tag` variable (first line)
* update the version in `Version:`
* add a line to the changelog
* date format: `LC_TIME=C date +"%a %b %d %Y"`, name address and version
* `new major release X.X`
In `CHANGELOG.md`, add a changelog entry for the new release with the format:
~~~
YYYY-MM-DD vX.Y:
* add: description...
* ...
* change: description...
* ...
* fix: description...
* ...
~~~
In `t/01-pga_version.t`, edit variable `$good_version`.
Update documentation using the following commands:
~~~
pod2text check_pgactivity > README
podselect check_pgactivity > README.pod
~~~
Update the `contributors` file with new contributors.
## Run tests
Run the tests against all possible PostgreSQL releases. At least the one
officially supported. Fix code or tests before releasing.
## Commit
Commit all these changes together with commit message: `Release X.Y`.
## Tagging and building tar file
Directly into the official repo:
~~~
TAG=REL2_4
git tag -a $TAG <Release commit number>
git push --tags
git archive --prefix=check_pgactivity-$TAG/ -o /tmp/check_pgactivity-$TAG.tgz $TAG
~~~
## Release on github
- Go to https://github.com/OPMDG/check_pgactivity/releases
- Edit the release notes for the new tag
- Set "check_pgactivity $VERSION" as title, eg. "check_pgactivity 2.4"
- Here is the format of the release node itself:
~~~
YYYY-MM-DD - Version X.Y
Changelog:
* item 1
* item 2
* ...
~~~
- Upload the tar file
- Save
- Check or update https://github.com/OPMDG/check_pgactivity/releases
## Building the RPM file
### Installation
~~~
yum group install "Development Tools"
yum install rpmdevtools
useradd makerpm
~~~
### Building the package
~~~
su - makerpm
rpmdev-setuptree
git clone https://github.com/OPMDG/check_pgactivity.git
spectool -R -g check_pgactivity/check_pgactivity.spec
rpmbuild -ba check_pgactivity/check_pgactivity.spec
~~~
The RPM is generated into `rpmbuild/RPMS/noarch`.
Don't forget to upload the package on github release page.
## Building the Debian package
Debian packaging is handled by the Debian Mainteners
(see https://salsa.debian.org/?name=check_pgactivity).
A new release will trigger the release of a new package.
### Community
## Packages
Ping packager on mailing list pgsql-pkg-yum if needed to update the RPM on PGDG repo.
## Nagios Exchange
Update:
* the release number
* the services list
* add latest packages, zip and tarball.
https://exchange.nagios.org/directory/Plugins/Databases/PostgresQL/check_pgactivity/details
Ask Thomas (frost242) Reiss or Jehan-Guillaume (ioguix) de Rorthais for credentials.
## Submit a news on postgresql.org
* login: https://www.postgresql.org/account/login/?next=/account/
* go https://www.postgresql.org/account/edit/news/
* click "Submit News Article"
* organisation: check_pgactivity project
* Title: "Release: check_pgactivity 2.4"
* Content:
~~~
check_pgactivity version 2.4 released
========================
check\_pgactivity is a PostgreSQL plugin for Nagios. This plugin is written with a focus
on a rich perfdata set. Every new features of PostgreSQL can be easily monitored with
check\_pgactivity.
Changelog :
* ...
* ...
* ...
Here are some useful links:
* github repo: [https://github.com/OPMDG/check_pgactivity](https://github.com/OPMDG/check_pgactivity)
* reporting issues: [https://github.com/OPMDG/check_pgactivity/issues](https://github.com/OPMDG/check_pgactivity/issues)
* latest release: [https://github.com/OPMDG/check_pgactivity/releases/latest](https://github.com/OPMDG/check_pgactivity/releases/latest)
* contributors: [https://github.com/OPMDG/check_pgactivity/blob/master/contributors](https://github.com/OPMDG/check_pgactivity/blob/master/contributors)
Thanks to all the contributors!
~~~
* check "Related Open Source"
* click on submit
* wait for moderators...
## pgsql-announce
Send a mail to the pgsql-announce mailing list. Eg.:
~~~
check_pgactivity v2.4 has been released on January 30th 2019 under PostgreSQL
licence.
check_pgactivity is a PostgreSQL plugin for Nagios. This plugin is written
with a focus on a rich perfdata set. Every new features of PostgreSQL can be
easily monitored with check_pgactivity.
Changelog :
* ...
* ...
* ...
Here are some useful links:
* github repo: https://github.com/OPMDG/check_pgactivity
* reporting issues: https://github.com/OPMDG/check_pgactivity/issues
* latest release: https://github.com/OPMDG/check_pgactivity/releases/latest
* contributors:
https://github.com/OPMDG/check_pgactivity/blob/master/contributors
Thanks to all the contributors!
~~~
## Tweets & blogs
Make some noise...
|
