JIRA already offers some semantic groupings via components
https://tools.oasis-open.org/issues/browse/OFFICE?report=com.atlassian.jira.plugin.system.project:components-panel
and some roadmap view, where issues are sorted by ODF version:
https://tools.oasis-open.org/issues/secure/BrowseProject.jspa?id=10027&subset=-1
^^some base to start.
I would be curious on the amount/work-load of errata an OASIS TC is
required to write for ISO.
If we would have stick with a train wagon model for specification,
like a time boxed deliver of versions, would it create errata
work-load for each wagon?
In the end we have to keep in mind, that the specification is driven
by the implementors. Otherwise we will share the fate as XHTML.
Till soon in the call,
Svante
Am 12.10.2013 02:13, schrieb Patrick Durusau:
Greetings!
In order to start moving effectively towards ODF 1.3, we need to:
1) Have a discussion about what to include in ODF 1.3, and
2) What should be included in ODF 2.0?
The ODF JIRA instance lists:
143 Open issues and,
219 New issues.
I will try to look at those categories more closely over the
weekend
and will post a summary of what possible groupings I see in the
issues.
Your groupings may (will?) differ from mine so please do take a
look
at JIRA when you can.
Don't want to rush to decisions but we do need to start moving in
the
direction of deciding on features, due dates, etc.
Hope everyone is at the start of a great weekend!
Patrick
>
>
---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS
TC that
> generates this mail. Follow this link to all your TCs in
OASIS at:
>
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
