Werner Lemberg pushed to branch master at FreeType / FreeType
Commits:
-
a4f3e858
by Anurag Thakur at 2023-08-25T21:36:12+02:00
-
4a0c5639
by Werner Lemberg at 2023-08-25T21:36:39+02:00
2 changed files:
Changes:
1 | +How to update the FreeType web pages
|
|
2 | +------------------------------------
|
|
3 | + |
|
4 | +The 'freetype.org' website is hosted via the 'freetype-web' repo
|
|
5 | +located at
|
|
6 | + |
|
7 | + https://gitlab.com/freetype/freetype-web ,
|
|
8 | + |
|
9 | +which in turn is a mirror from the master 'freetype-web' repository
|
|
10 | +located at
|
|
11 | + |
|
12 | + https://gitlab.freedesktop.org/freetype/freetype-web .
|
|
13 | + |
|
14 | +Due to Cloudflare caching, changes take time to appear on
|
|
15 | +'freetype.org', so visit
|
|
16 | + |
|
17 | + https://freetype.gitlab.io/freetype-web
|
|
18 | + |
|
19 | +for instant feedback.
|
|
20 | + |
|
21 | +All the commits should *only* be done to the 'freetype-web' repo at
|
|
22 | + |
|
23 | + https://gitlab.freedesktop.org/freetype/freetype-web
|
|
24 | + |
|
25 | +When a commit is done to this repo, the CI pipeline runs and the
|
|
26 | +website is deployed via gitlab pages at
|
|
27 | + |
|
28 | + https://freetype.pages.freedesktop.org/freetype-web .
|
|
29 | + |
|
30 | +The pull mirror automatically updates the repository in 'gitlab.com',
|
|
31 | +and the CI pipeline deploys the website at:
|
|
32 | + |
|
33 | + https://freetype.gitlab.io/freetype-web
|
|
34 | + |
|
35 | +Since the 'freetype.org' website uses Cloudflare caching, it will take
|
|
36 | +a while for the changes to show up in 'freetype.org'.
|
|
37 | + |
|
38 | +If you have access to the Cloudflare dashbouard you can purge the
|
|
39 | +cache from there; this will cause the cache to be fetched again
|
|
40 | +resulting in the website being updated instantly.
|
|
41 | + |
|
42 | +--- end of freetype-web.txt --- |
... | ... | @@ -5,7 +5,7 @@ How to prepare a new release |
5 | 5 | `FREETYPE_MINOR`, and `FREETYPE_PATCH`.
|
6 | 6 | |
7 | 7 | . Update version numbers in all files where necessary (for example, do
|
8 | - a grep for both '2.10.4' and '2104' for release 2.10.4).
|
|
8 | + a grep for both '2.13.2' and '2132' for release 2.13.2).
|
|
9 | 9 | |
10 | 10 | . builds/unix/configure.raw: Update `version_info`.
|
11 | 11 | |
... | ... | @@ -91,13 +91,14 @@ How to prepare a new release |
91 | 91 | zip!
|
92 | 92 | |
93 | 93 | . Run the following script (with updated `$VERSION`, `$SAVANNAH_USER`,
|
94 | - and `$SOURCEFORGE_USER` variables) to sign and upload the bundles to
|
|
95 | - both Savannah and SourceForge. The signing code has been taken from
|
|
96 | - the `gnupload` script (part of the 'automake' bundle).
|
|
94 | + `$SOURCEFORGE_USER`, and `GPG_KEY_ID` variables) to sign and upload
|
|
95 | + the bundles to both Savannah and SourceForge. The signing code has
|
|
96 | + been taken from the `gnupload` script (part of the 'automake'
|
|
97 | + bundle).
|
|
97 | 98 | |
98 | 99 | #!/bin/sh
|
99 | 100 | |
100 | - VERSION=2.12.0
|
|
101 | + VERSION=2.13.2
|
|
101 | 102 | SAVANNAH_USER=wl
|
102 | 103 | SOURCEFORGE_USER=wlemb
|
103 | 104 | GPG_KEY_ID=BE6C3AAC63AD8E3F
|
... | ... | @@ -183,7 +184,7 @@ How to prepare a new release |
183 | 184 | |
184 | 185 | #!/bin/sh
|
185 | 186 | |
186 | - VERSION=2.10.4
|
|
187 | + VERSION=2.13.2
|
|
187 | 188 | SOURCEFORGE_USER=wlemb
|
188 | 189 | |
189 | 190 | #####################################################################
|