[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [office] Next steps in completing ODF 1.2
I think it would be better to allow targeting new issues that address defects in CD05/CD06 to a CD07 and then decide whether there is to be no CD07 later (in which case the retargeting to ODF-Next will be inevitable). This provides important differentiation between issues that are intentionally created as ODF-Next items or are intentionally deferred already, versus ones where we might still deliberate on their importance for inclusion in a potential further ODF 1.2 draft. It would be helpful if we created the provisional CD07 target now (after discussion on Monday) so that it is available for straightforward usage. - Dennis -----Original Message----- From: Michael Brauer [mailto:michael.brauer@oracle.com] Sent: Friday, October 29, 2010 00:17 To: office@lists.oasis-open.org Subject: [office] Next steps in completing ODF 1.2 [ ... ] 1) After the TC call next Monday, we will retarget all new open ODF 1.2 issues to ODF-Next 2) We only accept new issues with a CD06 target under the following conditions: a) the issue comes with an uncontroversial resolution. (Uncontroversial will be mean that there are no "-1" votes in JIRA) b) or, the TC votes that the issue is important enough to further delay ODF 1.2. TC members can request an ODF 1.2 CD06 target on the mailing list. If that request is seconded by another TC member, the approval of the target takes place in the next TC call. Note that any specific issues deferred to ODF-Next may be re-targetted to CD 06 according to a) or b). After the TC call on Monday, November 8th, condition a) above is replaced by: a')the issue comes with an uncontroversial resolution. (Uncontroversial will be mean that there are no "-1" votes in JIRA) AND the candidate draft for the CD06 ballot has not yet been posted AND the Editor is able to integrate the resolution without further delaying the drafts. In other words, we always preserve the ability for the TC, via a majority vote, to open and resolve any issue, even if this results in a delay of ODF 1.2. However, we at the same time take steps to transition from the review and editing phase of ODF 1.2 to the final editing and approval stage. 3) The TC editor will prepare the final drafts after the November 8th call. This may actually take a few days, because the generated text has to be updated and consistency checks have to run. As soon as the final drafts are ready and no motions for resolving further issues do exist, the TC editor or chairs will make a motion for approval of the drafts as a Committee Specification Draft (CSD) and a follow-up 15-day public review. This means that the TC has another week to provide resolutions. From November the 8th on, we prepare the final drafts, and we only further delay ODF 1.2 in order to resolve further issues if a majority of TC members approved that. Best regards Michael -- Michael Brauer | Oracle Office Development Phone: +49 40 23646 500 Oracle Office GBU ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Rijnzathe 6, 3454PV De Meern, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven --------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]