As just noted, the sourceforge upgrade has its problems.

1. www.freecol.org seems to have reverted to something very basic.
www.freecol.org/administrator is still working and AFAICT the content is still 
all there in Joomla, but I could not work out how to get it all published 
again.  Any chance you can have a look Michael?

2. Despite the e-mail to contrary, they still claim to be importing our repo
at least according to: https://sourceforge.net/p/freecol/code/
However if you try a checkout it seems to be live.  Pity the URLs they supply 
are misleading and do not take account of the extra /freecol in the repo
(i.e. do not believe them when they say to do

svn checkout --username=mpope \ 
svn+ssh://mp...@svn.code.sf.net/p/freecol/code/trunk trunk

but use svn+ssh://mp...@svn.code.sf.net/p/freecol/code/freecol/trunk
however, I have not yet done a full import at this point)

3. They renumbered all the bug reports.  And presumably all the other trackers 
too.  <EXASPERATED-AUSSIE-EXPLETIVES/>

4. A fair bit of flakiness is occurring.  As a consequence of #3 I started 
going through the bug list checking that all the new labels and whathaveyou 
are sensible, but quite often a bug becomes mysteriously inaccessible for a 
while.

So, it is indeed not the end of the world, but at least some unwanted 
disruption.  Hopefully this will stabilize before I am back to work next week.

Cheers,
Mike Pope
 

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
Freecol-developers mailing list
Freecol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freecol-developers

Reply via email to