> ## Phasing out of old repositories > > 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?)
Not verifiable yet as they time out while fetching dependencies - but all are there: https://builds.apache.org/user/stain/my-views/view/taverna/ > 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/ This should now be done (let me know if you spot any that isn't!) Example: https://github.com/taverna/taverna-scufl2/ > 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). Done - the only changes I found where Alan's pom.xml changes for changing <dependencies> to OSGi bundles, as these were not up to date with the re-made pom.xml files on apache/incubator-taverna* and the new taverna-maven-parent. Thus I ignored these as they would not be mergeable across. Example: https://github.com/taverna/taverna3-command-line/commits/master -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
