Send kea-dev mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."


Today's Topics:

   1. Re:  Stable links to devel doc (Tomek Mrugalski)


----------------------------------------------------------------------

Message: 1
Date: Mon, 28 Aug 2017 13:59:39 +0200
From: Tomek Mrugalski <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] Stable links to devel doc
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

W dniu 25.08.2017 o 13:30, W?odzimierz Wencel pisze:
> As for dev docs we provide only for the current version at
> https://jenkins.isc.org/job/Kea_doc/doxygen it's updated every time
> after developers push changes to kea master branch and indexing should
> work there.
> 
> http://git.kea.isc.org/~tester/kea/doxygen/ is no longer maintained (and
> it actually should be removed).
> 
> We publish users guide for each version but never planned to do it with
> dev guide, the idea is that dev guide can be build from kea package if
> needed.
> 
> Is https://jenkins.isc.org/job/Kea_doc/doxygen really unusable for you?
Couple weeks ago I created a simple redirect here:

kea.isc.org/docs/devel/

It is expected to be stable. It currently forwards to jenkins. I'll
update it if we ever move the devel doc to a different location. It is
good enough if you want to point to top of the docs, but probably
useless if you need specific subpage.

Tomek


------------------------------

Subject: Digest Footer

_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev

------------------------------

End of kea-dev Digest, Vol 41, Issue 9
**************************************

Reply via email to