+1 Especially those old Adobe issues that were imported. To me they are mostly clutter because of the quantity, age, and missing attachments. I would much rather have a clean start. But brining in any new (from a given time range x number of months) wouldn't be a bonus, unless that's an entirely manual process.
-Mark K -----Original Message----- From: Carlos Rovira [mailto:carlosrov...@apache.org] Sent: Wednesday, January 9, 2019 4:32 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Enabling GitHub "Issues" and "Wiki" for flex repositories Hi Olaf, I like your idea. I think going to GitHub is like when we migrate from SVN to GIT, we must go with the times. Is like FlexJS vs Royale wiki. We started a new one with newer info in Royale, but still have useful content from FlexJS that we should not remove and migrate as we can. So for me is ok to star clean on Github and lock JIRA, (or just be able to close or update JIRA content, but be unable to create new ones on JIRA. People working in Flex should now that as part of the things they need to know. If want to create a new ticket, first check JIRA, but create from scratch or recreate in Github. This will be an improvement for Flex in the end just my 2... Carlos El mar., 8 ene. 2019 a las 23:18, Olaf Krueger (<m...@olafkrueger.net>) escribió: > > Are we going to say that we won't fix any of the bugs currently open in > JIRA?... > > My concern is having two active bug bases... > > We maybe could set or treat or freeze JIRA as read-only and could link to > the entire Flex-JIRA from GitHub in order to not losing the history. > If somebody is going to fix one of those existing JIRA issues we could > simply recreate it manually as a GitHub issue. > If somebody will file a new GitHub issue we may want to check if there's a > JIRA duplicate in order to link it from the GitHub issue. > But on the other hand, I don't believe when somebody creates a new JIRA > that > somebody checks if there's already a JIRA duplicate. > > Thoughts? > > Olaf > > > > -- > Sent from: http://apache-flex-development.2333347.n4.nabble.com/ > -- Carlos Rovira http://about.me/carlosrovira
