Publish a new release on PEAR and github?
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 91
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/php/phd/releases mentions the last release was 1.1.11, from 2019. Various improvements were made on the master branch since then (e.g. fixing various notices uses of deprecated features such as join() argument order).
https://wiki.php.net/doc/phd/install mentions that "The preferred method is using the pear channel", which also causes 1.1.11 to be installed.
I'm not familiar with publishing of pear modules myself, or who would be considered an owner of this application. Going through the steps in https://github.com/php/phd/blob/master/HOWTO.RELEASE first would help (e.g. checking for missing files and putting release notes in package.xml)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with HOWTO.RELEASE and inspect package.xml for missing files and release notes. Review the GitHub releases page and the PEAR installation note, then determine the release-owner and publishing steps. Done means a new release is published on GitHub and PEAR containing the improvements on master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100