download page links to sourceforge

[KaiMartin]

The download page of pcb still points to sourceforge for a download of the sources of the current release
http://pcb.gpleda.org/obtaining.html --> http://sourceforge.net/projects/pcb/files/

For consistency, it should link to http://geda.seul.org/dist/

---<)kaimartin(>---

[KaiMartin (kmk-familieknaak)]

I assigned myself to this very simple bug to get used to the procedure.. Will file the almost trivial patch later.

---<)kaimartin(>---

[KaiMartin (kmk-familieknaak)]

This patch replaces the link to sourceforge.net in obtaining.html with a link to http://geda.seul.org/wiki/geda:download

[Bert Timmerman (bert-timmerman)]

AFAICT, this patch is not committed in the gpleda.org/pcb.git repository.
Please revert the status to "In Progress" and find somebody to push this patch.

[Bert Timmerman (bert-timmerman)]

Please forgive my misunderstanding, the faulty link still lives on:

http://pcb.gpleda.org/obtaining.html

and does not live in the pcb source code repository at all.

[KaiMartin (kmk-familieknaak)]

Hi Bert.

ad 1)
My understanding of fix commited was "fix commited to the tracker". If this is meant to mean "fix commited to the repo" I should indeed choose a different status. I find "in progress" not really appropriate, too. I don't intend to work any more on it :-)
(What is the difference between "fix commited" and "fix released"? I mean, if the patch is pushed, is there yet another stage of approval?)

ad2)
The code for the web pages lives in git://git.gpleda.org/pcbhtdocs.git

---<)kaimartin(>---

[Peter Clifton (pcjc2)]

"Fix committed" means the fix is in the git repoository - presumably thinking about code here
"Fix released" means an official software release has been made which encorporates the fix, and users can get it.

For our websites, where commits to the git repository automatically sync to the website, we would not use the "Fix committed" state.

Thinking about this though.. I need to update my robot script to take account of this possibility!

[KaiMartin (kmk-familieknaak)]

The link to sourceforge is in obtaining.shtml, too. Here comes a second mini patch...

[Peter Clifton (pcjc2)]

If you'll forvgive me delaying these patches, I'd like to use them for some dummy-runs of the gpleda.org commit robot I've been working on.

I will have to get it installed on gpleda.org and tested first though!

[Krzysztof Kościuszkiewicz (k-kosciuszkiewicz)]

Peter, do you still want to use the bug for test-driving the commit robot?

[KaiMartin (kmk-familieknaak)]

Can we close this bug?

[Bert Timmerman (bert-timmerman)]

Hi all,

AFAICT the patch in #7 is still not pushed to the wiki page.

Another thing that could be mentioned are the nightly windows snapshots at:

ftp://ftp.delorie.com/pub/geda-windows/snapshots/

This requires a clear distinction between the link to the releases at sourceforge and the nightly snapshots for testing.

[DJ Delorie (djdelorie)]

Just out of curiousity, why is pointing to sourceforge a bug? That's the only place I upload releases.

Also, the geda:download page clearly says "there is no supported Windows version" which is incorrect for PCB (and gerbv, IIRC); I wouldn't want to mislead anyone.

[Bert Timmerman (bert-timmerman)]

Hi,

No progress in 3 years !

I'm closing this bug as downloads are ready are mentioned on the index page of http://pcb.geda-project.org.

Kind regards,

Bert Timmerman