Re: [Discuss] Move Storm from JIRA to GitHub Issues
(1) Because of tighter integration with code, I think it will be better to move to github issues.If we run into any limitations we can ask github to implement. (2) For storm, we will have to change some of the release tools/scripts that pull jiras and related PRs that will need to be changed to do the "right thing" in the github issues case. --Bipin On Monday, February 26, 2024 at 08:09:22 AM CST, Richard Zowalla wrote: Any additional thoughts? Am Donnerstag, dem 22.02.2024 um 12:21 +0100 schrieb Alexandre Vermeerbergen: > +1 I agree that JIRA is overkill for the simple needs of incidents / > enhancements tracking of Apache Storm > > Alexandre > > Le jeu. 22 févr. 2024 à 12:18, Richard Zowalla a > écrit : > > > > Hi all, > > > > The ASF JIRA instance no longer allows users to self-sign-up > > (though it > > DOES allow us to invite others). This is largely due to spam. > > Most developers have a GitHub account (and that is where most folks > > interact with Storm's code base), and this would meet folks where > > they > > are, as opposed to making them go somewhere else to dig through > > issues. > > > > Tentative suggestion: > > > > * Go through existing Storm JIRA issues and close any issues that > > are > > no longer relevant. > > * Migrate open issues to GitHub Issues in apache/storm (linking > > back to > > the > > JIRA issue) > > * All new issues will only be created in GitHub Issues > > * When an existing JIRA issue is fixed, it will be updated in both > > locations > > * Make JIRA read-only for normal users > > > > Potential process changes: > > * Release notes/change logs are currently generated through JIRA. > > We > > would need to change that. > > > > NOTE: This is not final; the above text is just to start the > > discussion. > > > > Feel free to pick holes in the above, suggest changes, or propose > > something else! > > > > Thoughts and feedback are welcome! > > Richard
Re: [PR] STORM-4035 - Remove ConfluentAvroSerializer (storm-hdfs) (storm)
jnioche merged PR #3627: URL: https://github.com/apache/storm/pull/3627 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [Discuss] Move Storm from JIRA to GitHub Issues
Any additional thoughts? Am Donnerstag, dem 22.02.2024 um 12:21 +0100 schrieb Alexandre Vermeerbergen: > +1 I agree that JIRA is overkill for the simple needs of incidents / > enhancements tracking of Apache Storm > > Alexandre > > Le jeu. 22 févr. 2024 à 12:18, Richard Zowalla a > écrit : > > > > Hi all, > > > > The ASF JIRA instance no longer allows users to self-sign-up > > (though it > > DOES allow us to invite others). This is largely due to spam. > > Most developers have a GitHub account (and that is where most folks > > interact with Storm's code base), and this would meet folks where > > they > > are, as opposed to making them go somewhere else to dig through > > issues. > > > > Tentative suggestion: > > > > * Go through existing Storm JIRA issues and close any issues that > > are > > no longer relevant. > > * Migrate open issues to GitHub Issues in apache/storm (linking > > back to > > the > > JIRA issue) > > * All new issues will only be created in GitHub Issues > > * When an existing JIRA issue is fixed, it will be updated in both > > locations > > * Make JIRA read-only for normal users > > > > Potential process changes: > > * Release notes/change logs are currently generated through JIRA. > > We > > would need to change that. > > > > NOTE: This is not final; the above text is just to start the > > discussion. > > > > Feel free to pick holes in the above, suggest changes, or propose > > something else! > > > > Thoughts and feedback are welcome! > > Richard signature.asc Description: This is a digitally signed message part
