> If Mike+David are ok with it being added THAT MUCH too late, I could add it 
 > to the website
> code in git soon? I'd also add the link to the front page.
I didn't realise the website was on your github accessible to the current team, 
that's good.
> I looked at the github repo and it seems he did a merge to the slim branch 
> there
> on 2019-11-08, which should be the manual trigger for another nightly release,
> according to the news item he wrote.
> It just seems there were no files/release produced, which I would guess means
> David would be needed to debug the travis stuff.

I had wondered why it had been so long since the last nightly release (when I 
can see you guys have been still actively working on the project over the 
year), hope you guys can get it working again.

> Still the january nightly is much more up to date than 0.11.6 and gets about 
>as many
> weekly downloads. With a website update more people might find it.
> Greetings,
> wintertime
Yup that's a big part of the main point I was pushing in my 'novel' lol. 
There's needs to be a link to the nightly releases in all high traffic areas 
such as website homepage, website news, website about/current status, website 
downloads, sourceforge homepage, and sourceforge forums (via pinned 
announcement thread).

More prominent links to discussion forum and where to report bugs in all high 
traffic areas is also HIGHLY recommended too.
No ones mentioned the Indiedb so I'm guessing the left over team don't know who 
was running it? the files in the downloads section don't have versions numbers 
but they are dated 2010 so you can bet they are super old! Anyone can add files 
to it thankfully so I could copy 0.11.6 there and then the latest nightly 
release too. But it would be better if the current team can regain full control 
of it.
https://www.indiedb.com/games/freecol/downloads

Regards

Blake
_______________________________________________
Freecol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freecol-developers

Reply via email to