[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ee4j-community] issue migration
- From: Derek Moore <derek.p.moore@xxxxxxxxx>
- Date: Thu, 08 Feb 2018 00:01:45 +0000
- Delivered-to: firstname.lastname@example.org
What about projects like Jersey that already had their own GitHub organization?
One important thing missing in this game plan is preserving forks and PRs.
Jersey has some very high value PRs that should not be lost in all of this shuffling.
Tons of github-forks and private clones will lose their `origin` remotes.
I have a date parsing PR to Jersey I've been working on for 4 years (and am about to pick back up). And I know there are important PRs for Jersey's proxy client, among other things.
Now that we have a few of our projects migrated to the eclipse-ee4j
GitHub organization, we plan to start migrating the issues for these
projects.Â We plan to migrate both open and closed issues, and will
preserve the issue numbers so that references to issues by number
will continue to be valid.
A few of the new projects already have issues filed for them.Â To
preserve issue numbers we're going to need to delete and recreate
these repositories to remove all the issues.Â This will require
these issues to be refiled after the old issues are migrated.
Hopefully this won't be a hardship.Â We'll also be locking the
ability to file new issues until the migration is complete.
We'll preserve as much information as possible when migrating the
issues, but it might not be possible to (for example) make the
migrated issues appear to have been filed by the original submitters.
The original issues in the javaee GitHub organization will be closed
as a part of the migration.Â A link to the migrated issue will be
added to the original issue.Â Note that closing the original issues
will cause notifications to those associated with the issue.Â We
won't be updating already closed issues, to prevent notifications
in those cases.Â Still, there are thousands of open issues in some
of our projects and this will generate a large number of notifications.
Once we debug our tools and process with this first batch of projects,
we hope this will all go more smoothly for the remaining projects.
Thanks for your patience and understanding!
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit