-
Notifications
You must be signed in to change notification settings - Fork 193
Meeting minutes 2021 12 02
Attendance: Radu Coravu, John Pashley, Robert Anderson, Lief Erickson, Jarno Elovirta, Frank Wegmann, Roger Sheen, William Gamboa, Bill Burns, Chris Papademetrious
Closing the door on 3.6
Project board for next release: https://github.com/orgs/dita-ot/projects/27
Major development over. New pull request opened this morning to bump OASIS grammar to latest. Doing cleanup of items in project board, some not tagged with milestone.
Release is effectively done; waiting for docs to complete, so we can update the docs submodule.
Will be first release in quite some time that is not done through Travis, so may need some manual intervention. Expecting there will probably be a few kinks in the new CI process for release, but everything can be done manually as needed.
Migration docs - could use help noting anything that was missed. The new strings format should be listed, as recommended but not (yet) required -- it will be required in the future, and we recommend updating when you are able.
What to highlight in release notes?
- Preserving ID in conref'ed content
- Preview of DITA 2.0 chunking
- Moving AXF / XEP plugins to their own repo? Probably no - we still ship them so invisible to most users. But worth noting that these could now be updated independently of our release schedule, if someone wanted to do that.
Minor grammar update in the last month, PR created today to update release. Just making a new attribute on the new titlealt element required that was already required by spec text (but not by grammar).
DITA 2.0 spec reviews going (within TC).
What's the next release -- 3.8 or 4.0? Talk about removing customization directory would likely mean 4.0.
Semantic Versioning means we don't make backwards incompatible changes in a minor release (like 3.8). Historically we've done that, but only small ones - basically could be an impact to XSLT, things like that, but no major hits.
Jarno would prefer 4.0 -- there are a lot of backwards incompatible cleanup items that would make the code better. Like typing XSLT with as everywhere, if we do that but plugins don't pass the right value, it may work now now but typing would block it. But, it would make code more readable and more robust, easier to customize going forward.
If we do go for 4.0, we'd really want to try and have a compelling new feature -- a big version bump just to break compatibility might not seem as attractive to others. Are there things people would be happy to see in a new version? Maybe addressing some pain point, even if it's not a big feature?
Can likely include a lot of DITA 2.0 features by a 4.0 release -- 2.0 will not be official, and some things may not be final, but we can get quite far with it.
Removing customization directories for PDF2 -- best if we can offer the new, better alternative at the same time. Taking away the customization directories, which are fragile and limit what we can do with the tool, but providing the simple template for customization.
Project boards: Project boards: https://github.com/orgs/dita-ot/projects/
Time to go through pull requests, issues tracker, determine how to handle open issues.
View the latest DITA Open Toolkit docs at www.dita-ot.org/dev.