I was looking for some information about some of the XML-RPC functions and
noticed there are functions in the web code such as XMLRPCdeployServer not
described in web/.ht-inc/xmlrpcdocs/xmlrpcWrappers_8php.html.  I couldn't
find anything in the release notes related to updating the files in
xmlrpcdocs and it doesn't look like xmlrpcdocs was updated for a while.
Should a step be added to regenerate this file with Doxygen?

As a side note, I don't see much information on the website or wiki related
to the RPC-XML API.  The information contained in xmlrpcWrappers_8php.html
is not presented nor are instructions telling people to look at the file in
the code.  Am I missing something?  If not, we need to document this.

-Andy



-Andy

On Tue, Feb 3, 2015 at 2:59 PM, Josh Thompson <[email protected]>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Just as an update - the 2.4 release is almost ready.  There are a few JIRA
> issues left to be closed.  After that, we can generate the change log for
> the
> release.  We have an installation script and upgrade script as well as web
> pages listing out the steps for both in case people need/want to manually
> do
> installs and upgrades.
>
> Dmitri's OpenNebula stuff still needs to be committed, but he's having some
> account problems that we're trying to get worked out.  If we can't sort
> things
> out in the next day or two, one of the other committers can commit things
> for
> him.
>
> Thanks to everyone for all the hard work so far!  Keep it up, we're almost
> there!
>
> Josh
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iEYEARECAAYFAlTRKK4ACgkQV/LQcNdtPQPYCwCeIbgDnEeRMBIMO2DCvOgGbAtR
> WSMAnRXsPpHpplWNpX/8Rl8vQdOdDWKC
> =RpJQ
> -----END PGP SIGNATURE-----
>
>

Reply via email to