Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] Specification committee repos
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

On Tue, 30 Jul 2019 at 09:46, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
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.

On Mon, 29 Jul 2019 at 20:33, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

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 am wondering what the status of the individual project specifications is? As in, when the specifications texts to replace the boilerplate specifications will be available and their issues migrated (such as the content of JTA*Specification.pdf from https://github.com/javaee/jta-spec and the issues under https://github.com/javaee/jta-spec/issues)

On Wed, 10 Jul 2019 at 19:42, Bill Shannon <bill.shannon@xxxxxxxxxx> 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:
As part of this migration, will the existing issues reported on specs be passed to the new repos too? For instance the issues under https://github.com/javaee/jta-spec/issues


On Tue, 9 Jul 2019 at 18:56, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
There are now 3 repos for us to use to get our various parts done.


# https://github.com/jakartaee/specifications

A "Hugo" site for inclusion in jakarta.ee via github submodule.  This would be where we put the specifications as per Wayne's prototype at https://github.com/waynebeaton/jakarta.ee/tree/specs/content/specs


# https://github.com/jakartaee/specification-committee

Another "Hugo" site for inclusion in jakarta.ee via github submodule.  This would be where we put the TCK Process 1.0, associated Guide and any other official Specification Committee documents.

Perhaps this could go in a location like so?

 - https://jakarta.ee/committee/spec

Wayne, do you have a preference?


# https://github.com/jakartaee/specification-tools

This is where we would put various things like scripts to do the signing of final binaries and automation of various tasks we need to do on all specification projects, such as create PRs for boilerplate spec creation.


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

_______________________________________________
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



_______________________________________________
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

Back to the top