Difference between revisions of "Council agenda 2013-11"
Jump to navigation
Jump to search
m (copied some stuff from agenda of 2013-10-21 conference call) |
(→Agenda topics) |
||
| Line 10: | Line 10: | ||
* P6 and Release structure | * P6 and Release structure | ||
| − | * Request from Ontology SIG | + | * Request from Ontology SIG [SR] |
| − | + | See paper at | |
* Development of Pure ODD (heads-up for F2F) [LB] | * Development of Pure ODD (heads-up for F2F) [LB] | ||
Revision as of 22:54, 21 October 2013
Agenda topics
- Discuss possible revisions to step-by-step instructions in release procedure
- Should step 1 (creating P5/ReleaseNotes/readme-X.X.X.xml) happen at the same time as step 4 (freeze on commits)?
- Should we do steps 1 through 5 farther in advance so we can check that the version numbers etc. show up in the right places in files resulting from the build process?
- Immediately after a release, should we change the version number in the repository to next release number (e.g., "2.5a", with "a" for "alpha") so people won't be confused looking at the last successful build and seeing the old version number. Then immediately before a release, when we put out the call to TEI-L to look for typos, we can change the "a" to "b" (e.g., "2.5b") and then when we actually release, remove the "b".
- Should we have the date of a build be auto-generated? It will make it clearer that people are looking at something that's evolving, and it will also make it easier to diagnose the occasional case where one of the Jenkins servers stops updating.
- proposals for <standoff> -- have Javier join the discussion?
- P6 and Release structure
- Request from Ontology SIG [SR]
See paper at
- Development of Pure ODD (heads-up for F2F) [LB]
- Reaching consensus with EEBO TCP [SR]
- Report on new Roma Specification [JC]
- Report on specification and estimated cost for XPointer resolver [HC/SB]
- Report on specification and estimated cost for oXygen front end for ODD [SB/EM]
- Cheatsheets: Short best/recommended practice documents
