tl;dr: The Apache git repositories for Taverna has now been realized and populated. Commit anything not in the old repositories during the next 48h.
See http://taverna.incubator.apache.org/code/ for details. (Note that the GitHub links will not start working until tomorrow morning as the mirroring is done nightly.) Committers, make sure you use the https links as they are the only ones with write access. You will probably want to figure out how to configure your git to stop asking for https password, as it's not possible to use ssh-keys with git at Apache. The most secure way of doing this depend on your operating system and git version. One way you should NOT do it (unless you have an encrypted home directory) is like this: stain@biggie-utopic:~$ cat .netrc machine git-wip-us.apache.org login stain password fishsoup protocol https If you have already been using the taverna-incubator GitHub repositories with the new org.apache.taverna groupIds etc, then the change should be as simple as: git remote set-url origin https://git-wip-us.apache.org/repos/asf/incubator-taverna-language.git If you have used the taverna GitHub repositories, then many repositories have been merged and have pom.xml and Java package modifications, so it is best to start again from a new checkout from the new git repositories and then move over your changes manually or through git remote+git merge. Each old repository should have a pre-incubator-* tag (let me know if not!) - you might want to rebase any uncommitted/branched work to that - if you then do then merging from the new checkout, it should usually take care of the file-renames (except for new files). For each repository, there is a PGP-signed tag called apache-import-20150217 that signifies the formal import from the software grant, for example: https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=tag;h=refs/tags/apache-import-20150217 This should correspond to a bunch of pre-incubator-* tags in the old repositories, plus any folder renames and pom.xml changes. You fill find the old tags in the repositories under old/ - e.g. old/dataflow-activity-1.5 -- usually these will have a prefix of whatever the old repository will have been. Any open branches I found will now just be tagged, e.g. old/wsdl-generic-3.0-20150106 -- feel free to re-open these as new branches on the Apache side - I have not done any attempt of rebasing these to the new master. I have removed write-access to http://github.com/taverna-incubator/ and will in 48 hours remove those staging repositories as soon as we have verified builds in Apache's Jenkins from the new Apache git repositories. (any volunteers?) I am also asking for a silent consensus (that is - scream out if you disagree!) to in 48 hours or later to clear the "master" branches of all relevant repositories under http://github.com/taverna/ I have a bunch of MOVE-branches ready to be pushed that look like this: https://github.com/taverna/taverna-maven-parent/tree/master .. that is, all files removed, and a single README with redirect. (Again, the github link here should start working tomorrow) If by then, I see any changes beyond the pre-incubator* tags, I will merge it into the new git repositories. After the point of the README you should not be committing anything to the old repositories (except on their "maintenance" branch for 2.x). -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
