|
Derek,
Jersey and Mojarra are on the cusp of being contributed to
Eclipse. We hope this happens within the next couple of weeks. It
would be great if you could move that work to the Eclipse project.
-- Ed
On 2/7/2018 4:01 PM, Derek Moore wrote:
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.
Sincerely,
Derek Moore
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
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community
|
