[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jta-dev] [jakarta.ee-spec] Specification committee repos
|
A few days back I found the issues were migrated to the Jakarta Transactions repo - thanks!!
Hi,
I wondered when the issues might be moved over? As I mentioned the comments are important to keep but I don't think the specific issue number is - either a script or even myself can just add a comment to the 14 issues to say where they came from before if that is OK?
Thanks,
Tom
Personally I think new issue numbers are fine. It sounds a bit dangerous to remove the Jakarta Transactions github project as we already have active development and have resolve issues to make progress on Jakarta process which link to project boards and so on.
I just went through the ones in the javaee/jta-spec repo and I think they were all migrated from JTA_SPEC issue tracker before anyway so I don't think the GitHub issue numbers are particularly important to keep in sync unless there is something you are aware of why people might need that. Ideally just adding a comment a bit like
https://github.com/javaee/jta-spec/issues/14#issuecomment-296920283 which says "this issue was migrated from
https://github.com/javaee/jta-spec/issues/14" or something like that would be great. I could probably do that by hand myself to be honest if it's not scriptable.
When you move the issues, are you able to move the comments too? That is important to be able to keep.
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