1. Documentation management:
- sphinx (now available at
http://www.slac.stanford.edu/exp/lsst/qserv/): eqsy to find in google,
versionable, but how-to maintain it for previous versions?
- trac: mostly out of date, difficult to version => only one
occurence of the documentation
- core/doc: could be moved to sphinx? (pandoc is a easy to use rst
converter)
- confluence: ??
- doxygen: publish it in http://www.slac.stanford.edu/exp/lsst/qserv/?
- how to maintain the doc? Need to have an overhead for each
ticket, or specific ticket?
2. Configuration management:
it's difficult to switch source dependencies in Qserv because we
want to be eups independant, so dependency path are hard-coded in Qserv
configuration at compile time.
if you want to use ~/src/xrootd/ you have to setup xrootd and then
run in Qserv dir
scons install
# and
qserv-configure --all (which remove th db)
# start Qserv
=> this is very complicated
eups would allow developers to switch their version only by
setuping xrootd and then restarting Qserv, this is unsafe because new
software version may not be compliant with
Qserv configuration and data, but very convenient in developement mode.
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
