 |
 |
Fabrice, I thought about it a bit more... I think it would be better to not add new dependencies that we never discussed/approved, even if it means a few days of cleanup of what was done in DM-627. Would it be possible to massage DM-627 so that it does not touch any logging code, release it, and implement logging based on our log module, without yaml, under a separate ticket? Does the tip of the master work / does it pass integration tests *without* DM-627? Even if it does not, I think I'd be tempted to just assume the Dec release is broken and cut a properly working release once DM-627 is fixed, sometime later in January. Sorry we are making you undo the work you have done over the break! Jacek ######################################################################## 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