EPICS Version 4 Telecon, 26-Jan-2016
Present: AJ, AA, DH, KK, GW, MK, MD
RL (off-line): 18.104.22.168 is correct. Sorry for the confusion.
RL (off-line): Started working on .
DH: Dave says end of the month for the patch release.
RL (off-line): +1 on Michael’s work. Should be applied to all modules.
DH: Should be all-or-nothing, across all modules.
MK: Module owners should do this, I’ve already done it in pvDatabaseCPP and exampleCPP
DH: MD has already done pvData, so I just have to do NT
MD: I’m happy to do it, probably an hour’s work for me.
AI on MD: Create pull requests for all modules, other than exampleCPP and pvDatabaseCPP, which moves the headers into a pv/ subdirectory.
AI on MK: Handle exampleCPP and pvDatabaseCPP.
MK: what’s the status of sharelib versions?
MD/AJ: there is an example to follow in pvDataCPP.
Those remaining are pvAccess, pvaSrv, pvCommon CPP.
AI on MK: exampleCPP and pvDatabaseCPP
AI on MD: remaining C++ modules
RL (off-line): Thread covers multiple separate issues. Needs more thought.
Maybe defer to F2F meeting?
TK: (offline) a day’s training is fine for ESS. Maybe a day before the EPICS meeting for training. Then v4 meeting 2-days.
AJ: Would it make sense to split the C++ and Java into separate sessions?
DH: For Michigan, we basically just did C++. And that seemed to make sense. Probably also have an additional little while on Java.
Consensus: the training will concentrate on C++, with probably only RPC examples in Java.
Consensus: The dates proposed by Bob, and communicated by Timo in email are fine. So if Timo can make it work w.r.t. off site, that’s fine.
We do need some indication of the conference hotel for US lab travel requests.
MK: would like AJ to look at pull request #7 pvDatabaseCPP.
AJ: Yes, will look at that.
MK: there was also an issue with generating the documentation
AJ: Hm, maybe Ralph would be better for that.
Note: Completed AIs are shown once in the list of the meeting in which they are recognized as completed. They are removed in the minutes of the following meeting.
See who can fund dbGroup
Write the one license file (using the MIT license in most cases)
Update your module to include copy of that one LICENSE. Update your headers to contain the header text.
ALL MODULE OWNERS
wait on 5
On your module pages, remove the current/previous links; replace “Working Draft” with version number of module, which has its own numbering scheme, like 5.0.2 for pvDataCPP. Eg “Version 5.0.2 18/Nov/2015”
ALL MODULE OWNERS
Change the C++ bundling to add creation of a tarfile that includes Base 3.15.x
Simplify Literature page and home page to help users find novice oriented documentation.
Usher the patch fix for buffer overflow through to release.
Prepare a list of course contents for ESS EPICS Meeting training, and practicalities