sourceforge miseries

[Bruno H. <br...@cl...>]

mercurial access to sourceforge is highly unreliable these days again:

$ hg in
comparing with ssh://ha...@hg.../p/clisp/clisp
^Cinterrupted!
$ hg in
remote: abort: there is no Mercurial repository here (.hg not found)!
abort: no suitable response from remote hg!
$ hg in
comparing with ssh://ha...@hg.../p/clisp/clisp
searching for changes
no changes found
$ hg push
pushing to ssh://ha...@hg.../p/clisp/clisp
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: abort: Transport endpoint is not connected
remote: transaction abort!
remote: rollback failed - please run hg recover
abort: unexpected response: empty string

And no report at https://twitter.com/sfnet_ops.

This is not the first time the hg server at sourceforge is acting miserably.

To me, this increases the priority of moving the source code repository
away from sourceforge.

We can consider the following options:

  a) Move it to savannah.gnu.org (yes, savannah supports hg, see
     http://hg.savannah.gnu.org/hgweb/?sort=lastchange ),

  b) Convert it to git and move it to savannah.gnu.org.

  c) Convert it to git and move it to gitlab.com.

Discussion:

- Advantage of a): Less work, can be realized in a short time frame.

- Advantage of b), c): Reduce the entry barrier for young developers
  (they all know how to use git, but hardly anyone uses mercurial).

Bruno