aniani/profanity
1
0
Fork 0
mirror of https://github.com/profanity-im/profanity.git synced 2024-11-03 19:37:16 -05:00
Code
07900e9617
profanity/RELEASE_GUIDE.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

84 lines
2.4 KiB
Markdown
Raw Normal View History

Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
# Release Guide
release guide: remove libmesode Deprecated
2022-10-12 10:39:20 -04:00
* Release libstrophe if required
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
* Run Unit tests: `make check-unit`
* Run Functional tests - Currently disabled
* Run manual valgrind tests for new features
* Build and simple tests in Virtual machines ideally all dists including OSX and Windows (Cygwin)
Update RELEASE_GUIDE.md
2019-01-16 06:29:24 -05:00
* Update Inline command help (./src/command/cmd_defs.c)
Update release guide Maybe should create a helper script for some tasks.
2022-09-13 06:19:16 -04:00
* Check copyright dates in all files
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
* Generate HTML docs (the docgen argument only works when package status is development)
`./profanity docgen`
Update release guide with libprofanity info
2019-06-11 01:45:11 -04:00
* Determine if libprofanitys version needs to be [increased](https://github.com/profanity-im/profanity/issues/973)
Update RELEASE_GUIDE.md
2019-01-16 06:29:24 -05:00
* Update plugin API docs (./apidocs/c and ./apidocs/python) need to run the `gen.sh` and commit the results to the website git repo
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
* Update CHANGELOG
* Update profrc.example
Mention DEV for doap in release guide
2023-07-12 08:09:55 -04:00
* Update profanity.doap (new XEPs and latest version). Look for `DEV` which marks what is done on the development branch.
Add 0.14.0 release to doap and fix links
2023-08-04 02:37:54 -04:00
* Add new release to profanity.doap
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
## Creating artefacts
* Set the correct release version in configure.ac:
```
AC_INIT([profanity], [0.6.0], [boothj5web@gmail.com])
```
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
* Set the package status in configure.ac:
Typo fixes
2023-08-03 02:26:23 -04:00
```
PACKAGE_STATUS="release"
```
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
release guide: Use proper order Otherwise version will not be correct in generated man pages.
2022-10-12 11:11:12 -04:00
* Update date and version in man pages
* Generate manpages for profanity commands (the mangen argument only works when package status is development)
`./profanity mangen`
These files should be added to the docs subfolder and added to git whenever a command changes.
Mention manpages in release guide
2021-01-09 02:34:44 -05:00
* Add generated command manpages: `git add docs/profanity-*.1`
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
* Commit
Update release guide Maybe should create a helper script for some tasks.
2022-09-13 06:19:16 -04:00
* Tag (0.1.2)
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
* Push
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
* Configure to generate fresh Makefile:
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
```
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
./bootstrap.sh && ./configure
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
```
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
* Generate tarballs:
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
```
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
make dist
make dist-bzip2
make dist-xz
make dist-zip
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
```
Fix spelling
2021-08-25 21:17:42 -04:00
* Set the package status back to dev:
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
```
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
PACKAGE_STATUS="development"
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
```
Update release guide Maybe should create a helper script for some tasks.
2022-09-13 06:19:16 -04:00
* Remove generated command manpages:
`git rm docs/profanity-*.1`
`git checkout HEAD -- docs/profanity-ox-setup.1`
docs/profanity.1 and docs/profanity-ox-setup.1 are handwritten.
Mention manpages in release guide
2021-01-09 02:34:44 -05:00
release guide: Use proper order Otherwise version will not be correct in generated man pages.
2022-10-12 11:11:12 -04:00
* Commit `Start new cycle`
autotools: fix `make dist` command Now, `make dist` can be used for generating tarballs. It simplifies making proper release tarballs. Also, it includes some files, that are removed in RELEASE_GUIDE.md: - apidocs/ - CHANGELOG - theme_template It is a good idea to include such a kind of documentation. Update RELEASE_GUIDE.md.
2019-03-04 11:26:28 -05:00
* Push
Reformat RELEASE_GUIDE as md and add more info
2019-01-15 07:57:05 -05:00
## Updating website
Fix spelling
2021-08-25 21:17:42 -04:00
* Make changes to the git repo including uploading the new artefacts at:
Update profanity repo URL Move from github.com/boothj5/* to github.com/profanity-im/*
2019-05-03 04:51:28 -04:00
https://github.com/profanity-im/profanity-im.github.io
Update release guide Maybe should create a helper script for some tasks.
2022-09-13 06:19:16 -04:00
* Add .xz and .zip tarballs to `tarballs` directory
* Copy `guide/latest` to `guide/newversion`
* Update tarball location and name in index.html
* Update checksums in index.html
Mention profnaity_version in release guide
2020-07-09 11:03:05 -04:00
* Update profanity_version.txt
Add doap to release guide
2022-02-22 10:12:10 -05:00
* Take results from profanity.doap and put them into xeps.html
Copy Permalink