Skip to content
GitLab
Explore
Sign in
Register
FreeType
FreeType
Compare revisions
920c5502cc3ddda88f6c7d85ee834ac611bb11cc to 4a0c5639f7d6ab8b36e0f3989c76d09b2604e5b6
Commits on Source (2)
docs/freetype-web.txt: New file.
· a4f3e858
Anurag Thakur
authored
Aug 25, 2023
and
Werner Lemberg
committed
Aug 25, 2023
a4f3e858
docs/release: Minor fixes.
· 4a0c5639
Werner Lemberg
authored
Aug 25, 2023
4a0c5639
Hide whitespace changes
Inline
Side-by-side
docs/freetype-web.txt
0 → 100644
View file @
4a0c5639
How to update the FreeType web pages
------------------------------------
The 'freetype.org' website is hosted via the 'freetype-web' repo
located at
https://gitlab.com/freetype/freetype-web ,
which in turn is a mirror from the master 'freetype-web' repository
located at
https://gitlab.freedesktop.org/freetype/freetype-web .
Due to Cloudflare caching, changes take time to appear on
'freetype.org', so visit
https://freetype.gitlab.io/freetype-web
for instant feedback.
All the commits should *only* be done to the 'freetype-web' repo at
https://gitlab.freedesktop.org/freetype/freetype-web
When a commit is done to this repo, the CI pipeline runs and the
website is deployed via gitlab pages at
https://freetype.pages.freedesktop.org/freetype-web .
The pull mirror automatically updates the repository in 'gitlab.com',
and the CI pipeline deploys the website at:
https://freetype.gitlab.io/freetype-web
Since the 'freetype.org' website uses Cloudflare caching, it will take
a while for the changes to show up in 'freetype.org'.
If you have access to the Cloudflare dashbouard you can purge the
cache from there; this will cause the cache to be fetched again
resulting in the website being updated instantly.
--- end of freetype-web.txt ---
docs/release
View file @
4a0c5639
...
...
@@ -5,7 +5,7 @@ How to prepare a new release
`FREETYPE_MINOR`, and `FREETYPE_PATCH`.
. Update version numbers in all files where necessary (for example, do
a grep for both '2.1
0.4
' and '21
04
' for release 2.1
0.4
).
a grep for both '2.1
3.2
' and '21
32
' for release 2.1
3.2
).
. builds/unix/configure.raw: Update `version_info`.
...
...
@@ -91,13 +91,14 @@ How to prepare a new release
zip!
. Run the following script (with updated `$VERSION`, `$SAVANNAH_USER`,
and `$SOURCEFORGE_USER` variables) to sign and upload the bundles to
both Savannah and SourceForge. The signing code has been taken from
the `gnupload` script (part of the 'automake' bundle).
`$SOURCEFORGE_USER`, and `GPG_KEY_ID` variables) to sign and upload
the bundles to both Savannah and SourceForge. The signing code has
been taken from the `gnupload` script (part of the 'automake'
bundle).
#!/bin/sh
VERSION=2.1
2.0
VERSION=2.1
3.2
SAVANNAH_USER=wl
SOURCEFORGE_USER=wlemb
GPG_KEY_ID=BE6C3AAC63AD8E3F
...
...
@@ -183,7 +184,7 @@ How to prepare a new release
#!/bin/sh
VERSION=2.1
0.4
VERSION=2.1
3.2
SOURCEFORGE_USER=wlemb
#####################################################################
...
...