search

apache / cordova-coho

Apache Cordova coho
Apache License 2.0
33 stars 62 forks source link

Track releases in GitHub issues! #190

Open brodycj opened 6 years ago

brodycj commented 6 years ago

The documented procedure is to use JIRA issues when publishing tools, platforms, or plugins releases. Now that GitHub issues are enabled I would much rather track release items there and we cannot raise new JIRA issues, we are now forced to track release items in GitHub issues. I think we should check impact on areas such as:

brodycj commented 6 years ago

Bump with some additional comments:

I think that for each package release we should raise issues in https://github.com/apache/cordova/issues. Track all package release issues in one place, no more change for collision in GH issue numbers, etc.

An example where this went wrong: https://github.com/apache/cordova-docs/pull/886#issuecomment-423270720 / https://github.com/apache/cordova-docs/pull/886#issuecomment-423271940

janpio commented 6 years ago

Are issues for releases really necessary? What purpose did those JIRA tickets fulfill? Wouldn't it maybe make more sense to create milestones in the repositories and add all the PRs (and issues) included?

brodycj commented 6 years ago

Any pointers how to use milestones?

Also JIRA numbers made it relatively easy to reference issue number in git and svn commits. Any ideas how we can do this with milestones?

janpio commented 6 years ago

Any pointers how to use milestones?

Best start here: https://help.github.com/articles/creating-and-editing-milestones-for-issues-and-pull-requests/

Also JIRA numbers made it relatively easy to reference issue number in git and svn commits. Any ideas how we can do this with milestones?

Why do or did we need this? What is the benefit vs. just using the version number or the release we are working on?

brodycj commented 6 years ago

Why do or did we need this? What is the benefit vs. just using the version number or the release we are working on?

Using numbered issues makes it easier to track discussions if necessary. Maybe this is not really needed.

If we use release number, and which component is not obvious somewhere, I think we should be sure to also use the component name. This point may sound obvious but I think it should not be forgotten.

janpio commented 6 years ago

Using numbered issues makes it easier to track discussions if necessary. Maybe this is not really needed.

Each pull request or issue has a number on GitHub. They also have unique cross platform names that are generated on pasting a link to one.

If we use release number, and which component is not obvious somewhere, I think we should be sure to also use the component name. This point may sound obvious but I think it should not be forgotten.

Outside of a repo, versions (or milestones) have to be prefixed with the package, yes.