Tom,
We can migrate those issues. There aren't too many in the case of
JTA. There are 14. In order to do the migration and keep issue
numbers consistent, we will have to remove the repository and
recreate it (migrate the issues, then restore the content). Do you
think that's important? I can check if we can just move them and
regenerate them with new Issue IDs, if you think that would be
acceptable.
-- Ed
On 7/29/2019 7:25 AM, Tom Jenkinson
wrote:
I believe there's only a few specs for
which there was no repository to migrate the issues to until
recently. And yes, we still plan to do the issue migration
for these few repositories. Note that the issue migration
requires that there are no issues or pull requests in the
destination repository, so sometimes we have to destroy the
repository and recreate it to empty out the issues to allow
the issue migration to preserve issue numbers
Tom
Jenkinson wrote on 7/10/19 2:09 AM:
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
|