-
Notifications
You must be signed in to change notification settings - Fork 163
How to release Cypht
Marc Laporte edited this page Jul 7, 2023
·
20 revisions
This page is to document the steps to generate a Cypht release.
Scripts to evaluate:
- https://github.com/cypht-org/cypht/blob/master/scripts/code_check.sh
- https://github.com/cypht-org/cypht/blob/master/scripts/release_changes.sh
- https://github.com/cypht-org/cypht/blob/master/scripts/commit_check.sh
Steps for 1.4.x
- Release a version of https://github.com/cypht-org/php-sieve-manager and use that in Cypht
- Create branch 1.4.x and make necessary commits in this new branch
- "stability": "dev", in composer.json even though it doesn't exist in https://getcomposer.org/doc/04-schema.md
- Release 1.4.0 ** https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
- Update documentation to reflect that we now have 1.4.x and master. Ex.: https://github.com/cypht-org/cypht/blob/master/INSTALL
Important URLs for Cypht 1.3.0
- https://github.com/cypht-org/cypht/releases/tag/v1.3.0
- https://packagist.org/packages/jason-munro/cypht#v1.3.0
- https://github.com/cypht-org/cypht/tree/release-1.3.0
- https://github.com/cypht-org/cypht/tree/v1.3.0
Deprecated:
- We won't use anymore: https://github.com/cypht-org/cypht/blob/master/scripts/build_changelog.sh