mirror of
https://github.com/joomla-extensions/weblinks.git
synced 2025-01-26 22:08:27 +00:00
Updated the contribution / release guide from Phing to JoRobo (#224)
This commit is contained in:
parent
1680ec7b49
commit
74b200a632
17
.github/CONTRIBUTING.md
vendored
17
.github/CONTRIBUTING.md
vendored
@ -29,19 +29,12 @@ If you find any new bugs, or want to raise any type of support issue, please use
|
||||
|
||||
## Release Procedure
|
||||
|
||||
This is the procedure and checklist for creating a new package.
|
||||
This is the procedure and checklist for creating a new package:
|
||||
|
||||
* Update the version number in `build.ini`.
|
||||
* Run `phing set-version`.
|
||||
* Pun `phing` to make the new package for the version.
|
||||
* Run `phing tag`.
|
||||
* Push the commits and tags up to Github.
|
||||
* Go to the releases page on Github.
|
||||
* Click on the new tag.
|
||||
- Click the `Edit Tag` button.
|
||||
- Fill in the title and description for the release.
|
||||
- Attach the zip-file for the package to the release. Wait for the file to complete uploading!
|
||||
- Click the `Publish Release` button.
|
||||
* Update the version number in `jorobo.ini`
|
||||
* Modify `jorobo.ini`, add your GitHub token and add ` Release` after `Package`
|
||||
* Run `robo build` to make the new package and auto-upload and release it on GitHub.
|
||||
* Go to the releases page on GitHub, review the Changelog and change the status from Pre-Release to Stable.
|
||||
* Create a new `<update>` tag in the `manifest.xml` file.
|
||||
- Change the `<version>` tag to the new version.
|
||||
- Change the `<downloadurl>` tag to match the URL of the new release.
|
||||
|
Loading…
x
Reference in New Issue
Block a user