Since we all agreed here, I will now open the GitHub issues and discussions in the next few days. If you're faster than me, feel welcome to do it earlier. 😉
- Ben On Thu, 27 Apr 2023, 14:39 Benjamin Marwell, <bmarw...@apache.org> wrote: > +1 for starting fresh. > Since github is easier to get to, we will soon have enough issues to work > on. ;-) > > > Am Mi., 26. Apr. 2023 um 17:31 Uhr schrieb Colm O hEigeartaigh < > cohei...@apache.org>: > >> +1, especially since new users having to manually be approved to signup >> to JIRA. >> >> Colm. >> >> On Wed, Apr 26, 2023 at 3:38 PM Brian Demers <brian.dem...@gmail.com> >> wrote: >> > >> > That's a great point! >> > Nothing is stopping us from cutting over to GH now and then figuring out >> > the JIRA migration in the future (or not). 🤔 >> > >> > >> > On Wed, Apr 26, 2023 at 6:23 AM Francois Papon < >> francois.pa...@openobject.fr> >> > wrote: >> > >> > > Hi Brian, >> > > >> > > Thanks for sharing that! >> > > >> > > I think we could start by making JIRA read-only start fresh in GH, it >> > > would be the less effort way for us. >> > > >> > > regards, >> > > >> > > François >> > > >> > > > I don't think we need something as complex as this, but some linked >> > > threads >> > > > make good points about only needing to search one location to see >> > > history. >> > > > >> > > > Infra mentioned some projects just mark JIRA read-only and start >> fresh in >> > > > GH. >> > > > >> > > > I'll try to dig through the Arrow migration scripts a bit more and >> get a >> > > > better feel for the complexity/effort involved here. >> > > > >> > > > >> > > > If anyone has other thoughts or opinions on the topic, please let us >> > > know! >> > > > -Brian >> > > > >> > > > On Wed, Apr 5, 2023 at 9:24 AM Jean-Baptiste Onofré < >> j...@nanthrax.net> >> > > wrote: >> > > > >> > > >> +1 for me, no objections. >> > > >> >> > > >> Regards >> > > >> JB >> > > >> >> > > >> On Fri, Mar 31, 2023 at 3:40 PM Brian Demers <bdem...@apache.org> >> > > wrote: >> > > >>> We received a suggestion from the last board report to consider >> > > switching >> > > >>> from JIRA to GitHub issues. >> > > >>> >> > > >>> 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 Shiro'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 Shiro JIRA issues and close any issues that >> are >> > > no >> > > >>> longer relevant. >> > > >>> * Migrate open issues to GitHub Issues in apache/shiro (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 >> > > >>> Potential process changes: >> > > >>> * Release notes/change logs are currently generated through JIRA. >> > > (There >> > > >>> has been some discussion in the ASF Slack about using JReleaser, >> which >> > > >> can >> > > >>> generate a change log) >> > > >>> >> > > >>> 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! >> > > >>> >> > > >>> -Brian >> > > >> >
