Skip to content

Commit 440315f

Browse files
authored
added instructions on how to create a release
1 parent f2e2796 commit 440315f

1 file changed

Lines changed: 34 additions & 1 deletion

File tree

docs/NewPopplerRelease.md

Lines changed: 34 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,6 +235,9 @@ on your local machine type:
235235
Then back on your new AWS EC2 machine type:
236236

237237
cd
238+
./dobuildPoppler
239+
./doinstallPoppler
240+
238241
sudo apt install ./<<debian package name>>
239242

240243
(note the `./` is *required* for apt to install from a *local* package).
@@ -255,4 +258,34 @@ If all goes well you can then release the code....
255258

256259
### Releasing a new pdf2htmlEX version
257260

258-
TBD ;-(
261+
If you have release permissions, go the the pdf2htmlEX
262+
[releases](https://github.com/pdf2htmlEX/pdf2htmlEX/releases)
263+
page and click on the "Draft new release" button.
264+
265+
Choose an appropriate release/tag name. To make it simple
266+
for all users, please ensure the release/tag name *begins*
267+
with a `v` is then followed by the pdf2htmlEX version being
268+
released (as recorded in line 13 of the
269+
[CMakeLists.txt](https://github.com/pdf2htmlEX/pdf2htmlEX/blob/master/CMakeLists.txt)
270+
file) which is then followed by `-poppler-` and the poppler
271+
version used to build this version of pdf2htmlEX.
272+
273+
A typical release/tag should look like:
274+
275+
v0.18.1-poppler-0.75.0
276+
277+
Then in provide a description of what this new release
278+
contains. You might also include some simple installation
279+
instructions.
280+
281+
You should also upload any associated Debian package archives
282+
you created in the previous steps, along with their associated
283+
md5 and sha256 check sum fingerprints.
284+
285+
Finally, when all of the release information is correct, click
286+
on the "Publish release" button.
287+
288+
### You are now done!
289+
290+
Relax :-)
291+

0 commit comments

Comments
 (0)