Chronological Thread 

< Chronological >      < Thread >

---

Correction is needed on the URL to the teaching instance, it is
http://teaching.physiomeproject.org/

Regards,
Tommy.

On 13/02/15 15:15, Tommy Yu wrote:

Hi,

Continuing on the previous announcement, I have completed the code required
for conversion of Mercurial workspaces to Git workspaces and have proceeded
with this procedure on the staging instance of the Physiome Repository (at
http://staging.physiomeproject.org). Documentation will be done using this
instance for the mean time however please do help with the testing by making
use of the workspaces using any git client.

The teaching instance (http://teaching.physiomeproject.com/) has been
temporarily split from this to not disrupt some existing testing work for
some other projects, so the workspaces there are still backed by Mercurial.

Barring any problems resulting from testing, we plan to make a new release
some time early March that will effectively result in a Physiome Repository
backed completely by Git for the DVCS backend. The release will naturally
include the new features developed, such as the Collection+JSON based web
services.

Once again, please report any issues via the Physiome tracker or via this
mailing list.

Regards,
Tommy.

On 04/02/15 17:46, Tommy Yu wrote:

Hi,

In the interest of unification and consolidation of the tools to the
ones that other related communities have settled on, the Physiome
Repository will be migrating all its workspaces from Mercurial to
Git, as the latter is the DVCS of choice for the main developers of
various tools and various other tools have integration with git
rather than mercurial (such as figshare partnering with GitHub and
Mozilla, and that MAP Client is also migrating to git to be alongside
with its plugins).

The migration will be lossless, just that the access method will
change. All your data in your workspaces will become accessible
using a git client rather than a mercurial client once the migration
process is done.

As for the workspaces that embed others using mercurial
subrepository, the ones hosted on Physiome Repository will be
converted into git with the embedded workspaces be converted into git
submodules. The concept remains the same, just that the command line
syntax will be different. Your personal copies will remain as
mercurial on your disk, which means if you wish to take advantage of
the automatic conversion please push the data you have to your copy
on the Physiome Repository before the migration date. Alternatively,
you may use a git to mercurial bridge to continue your usage of
mercurial.

For the documentation side of things, they will be written once the
migration process is ready to happen. We plan to do this migration
some time late February to early March. A test migration will be
done on a new staging instance for demonstration purposes, and this
will go online some time mid-February.

If you have any questions or concerns, please reply to this
thread/list or contact me directly.

Regards, Tommy.

---

• [cellml-discussion] Physiome Repository backend conversion from mercurial to git, Tommy Yu, 02/04/2015
  • Re: [cellml-discussion] Physiome Repository backend conversion from mercurial to git, Tommy Yu, 02/13/2015
    • Re: [cellml-discussion] Physiome Repository backend conversion from mercurial to git, Tommy Yu, 02/13/2015
      • [cellml-discussion] What's the best way to comment on / ask about specific models?, Michael Clerx, 02/14/2015
        • Re: [cellml-discussion] What's the best way to comment on / ask about specific models?, David Nickerson, 02/14/2015
          • Re: [cellml-discussion] What's the best way to comment on / ask about specific models?, Michael Clerx, 02/15/2015
            • Re: [cellml-discussion] What's the best way to comment on / ask about specific models?, Randall Britten, 02/16/2015

---

Archive powered by MHonArc 2.6.18.