Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

community: open issues here for any significant old issue from JIRA #62

Closed
SethTisue opened this issue Jul 17, 2015 · 8 comments · Fixed by #196
Closed

community: open issues here for any significant old issue from JIRA #62

SethTisue opened this issue Jul 17, 2015 · 8 comments · Fixed by #196
Assignees
Milestone

Comments

@SethTisue
Copy link
Member

SethTisue commented Jul 17, 2015

today I closed all open XML tickets in the Scala JIRA: 9047, 8834, 7796, 7726, 7395, 7311, 7282, 6800, 6741, 6341, 5775, 5133, 5132, 5131, 5101, 4865, 4836, 4543, 4529, 4528, 4520, 4303, 4296, 4286, 4267, 4050, 3881, 3689, 3573, 3527, 3336, 3334, 3286, 3246, 3062, 2725, 1787, 1654

many of these ought to become issues here in this repo on GitHub. interested community members are invited to open new issues for them here, with links in both directions

EDIT: there is a list below of still-unmigrated issues

@biswanaths
Copy link
Contributor

Thanks @SethTisue for the help.
I will go through the issues and start creating them here.

@biswanaths
Copy link
Contributor

I was searching if there was a migration story for issues for libraries. At least scala-parser-combinator also have to deal with the same issue[1]. Let me see if there is any easier way to migrate JIRA to github. At least, description + linking(and back to github) to JIRA should be good enough.

[1]. scala/scala-parser-combinators#61

@SethTisue
Copy link
Member Author

scala-swing, too. if you could find a solution, that'd be great.

@biswanaths
Copy link
Contributor

This hack of the script( https://gist.github.com/biswanaths/23b13af64ef8b93af562) can do

  1. Create github issue given a jira issue.
  2. Will create the description in the github issue as same as jira issue.
  3. Create a link to jira issue in the github issue.
  4. Create a comment in jira issue pointing to github issue.

It does not migrate comments or any other useful information. Please see

  1. https://github.com/biswanaths/scala_jira_gh/issues , issue which are migrated from JIRA
  2. https://issues.scala-lang.org/browse/TEST-14 , for a sample of comment which will get applied to individual jira cases. For the test run all the back link to github were added to Test-14.

Please let me know, if community has any concerns or suggestions.

@mbeckerle
Copy link

I migrated several:

Original tickets are:
https://issues.scala-lang.org/browse/SI-7796 - XMLEventReader does not handle ' properly
https://issues.scala-lang.org/browse/SI-3527 - XML ConstructingParser too aggressive trimming whitespace around character references
Note: This one says fixed in Scala 2.11.7 - https://issues.scala-lang.org/browse/SI-3368 - Preserve CDATA sections, don't convert them to generic Text nodes.
https://issues.scala-lang.org/browse/SI-4303 - PrettyPrinter strips newlines from text in nodes, even pcdata
https://issues.scala-lang.org/browse/SI-4543 - PrettyPrinter removes newlines

The new issues are:

#72
#73
#75
#76
#77

The above are the issues as they appear now at github scala-xml community.

Note that #74, corresponding to https://issues.scala-lang.org/browse/SI-3368, was created, but both issues are closed as this was resolved before the migration of scala-xml to github.

@SethTisue SethTisue self-assigned this Feb 20, 2018
@SethTisue
Copy link
Member Author

I'll make this a README addition instead.

@SethTisue SethTisue added this to the 1.1.1 milestone Feb 20, 2018
SethTisue added a commit to SethTisue/scala-xml that referenced this issue Feb 21, 2018
@SethTisue
Copy link
Member Author

SethTisue commented Feb 21, 2018

we closed this ticket since the README here now calls attention to issue migration.

remaining unmigrated issues:

@SethTisue
Copy link
Member Author

Note that GitHub now allows you to transfer issues between repos with the same organization. I can transfer and reopen any of the above upon request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants