-
-
Notifications
You must be signed in to change notification settings - Fork 18
Expand file tree
/
Copy pathNEWRELEASE
More file actions
22 lines (19 loc) · 1015 Bytes
/
NEWRELEASE
File metadata and controls
22 lines (19 loc) · 1015 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Process to make a new PCP release
=================================
Steps to create the packages for a new release
----------------------------------------------
1. Update CHANGELOG with release notes
2. Tag release in git (tagged and signed using pcp-maintainers key)
Ex: git tag -s -u DEA2C114 -m X.Y.Z X.Y.Z
3. For the official Debian uploads by Debian developers
export DEB_SIGN_KEYID=0xFE0842EE36DD8C0C
./Makepkgs --signed --with-python3=yes --with-systemd=yes
4. For the official Fedora uploads by Fedora developers,
use official spec (as redhat.spec) and build with fedpkg.
Steps to update the webpage for the new release
-----------------------------------------------
1. From the end of index.haml replace the previous last PCP news
with a short note about the new release (moved to the front).
Update the website via "make && make install" (see README).
2. Send an email to pcp-announce@groups.io and pcp@groups.io with
the details of the new release (include the full changelog).