kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

Hi Carsten,

Do we still we still build and deploy the old 5.1 developer docs 
anywhere?  I guess I should remove them just in case someone else does. 
 I should be able to get to this shortly.

Thanks,

Wayne

On 10/26/21 2:18 PM, Carsten Schoenert wrote:
> Hello Wayne,
>
> Am 26.10.21 um 13:32 schrieb Wayne Stambaugh:
> > I just pushed the 5.1.11 tag to the 5.1 branch so please tag all of the
> > other repos so we can start the packaging process.  Please let me know
> > if there are any issues that would delay the tagging.
>
> I guess the loss of kicad-pcb.org isn't incorporated yet into this tag.
>
> > carsten@i5:~/gitprojects/kicad-upstream/kicad [(5.1.11)] $ git grep 
> > "kicad-pcb\.org"
> > Documentation/development/compiling.md:[download]: 
> > http://kicad-pcb.org/download/
> > Documentation/development/compiling.md:[KiCad website]: 
> > http://kicad-pcb.org/
> > Documentation/development/pcbnew-plugins.md:documentation](http://docs.kicad-pcb.org/stable/en/pcbnew.html#_kicad_scripting_reference). 
> >
> > Documentation/development/pcbnew-plugins.md:[here](http://docs.kicad-pcb.org/doxygen-python/namespacepcbnew.html). 
> >
> > Documentation/development/road-map.md:[kicad-website]:http://kicad-pcb.org/ 
> >
> > Documentation/development/road-map.md:[kicad-docs]:http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/index.html 
> >
> > Documentation/development/stable-release-policy.md:added to either the 
> > KiCad developer's site on Launchpad or the main website at 
> > www.kicad-pcb.org.
> > Documentation/development/testing.md:[trace mask documentation]: 
> > http://docs.kicad-pcb.org/doxygen/group__trace__env__vars.html
> > Documentation/development/testing.md:[trace mask documentation]: 
> > http://docs.kicad-pcb.org/doxygen/group__trace__env__vars.html
> > Documentation/development/testing.md:[advanced config documentation]: 
> > http://docs.kicad-pcb.org/doxygen/namespaceAC__KEYS.html
>
> I think you will agree that it would be good to fix this also within the 
> devel information resources before releasing a new version.