[
https://issues.apache.org/jira/browse/ODFTOOLKIT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215547#comment-13215547
]
Svante Schubert commented on ODFTOOLKIT-305:
--------------------------------------------
I quoted the change to show that there was a change without any reason and now
appeared without fix, to prove the random factor.
The main point was doing a code generation with a schema that has not changed
should not result into any changes, what it has.
I can not remember a CTR discussion nor find it, there was something in our
Wiki, but I can not find it.
Instead I asked back and CTR seems to be the default at Apache as Subversion
is bad in merging and working with patches. The master trunc is seen as
relative unstable at Subversion projects I been told, which seems quite the
opposite to the agile goal to be able to deliver at any time.
I thought, that if there is a comment on the issue, the comment should be
clarified before continue.
I would suggest that we discuss it on the list to be certain how we proceed.
Usually I prefer to have a 72 hour review (for small patches a week for larger)
for this project. Especially as the patches are not rushing in so fast we can
not wait. But perhaps Subversion is not designed for efficiently doing reviews
(see Linus Torvalds talk on GIT http://www.youtube.com/watch?v=4XpnKHJAok8).
IMHO we should switch to GIT anyway ASAP (different topic).
I found as references about the Apache way regarding to this only at:
http://www.apache.org/dev/new-committers-guide.html#responsibilities
http://www.apache.org/foundation/how-it-works.html#decision-making
And I read about a do-acricy that those who do the work have more influence.
This is obviously you doing the most work here at this project. But as soon the
master is stable, I am going to add some fixes that had been idling for a
while, like the JDK7 problem.
Finally, of course it is an OASIS schema, after writing the line, the idea
raised to fix this and I have triggered a mail already two days ago.
http://lists.oasis-open.org/archives/office/201202/msg00007.html
I might have posted this link earlier to avoid confusion.
No, need to rollback your fix. It was randomized before and it randomized now.
Those, who are working on those Java sources, should have a close eye on this
change.
PS: How is it possible to comment a comment in JIRA?
> Update ODF 1.2 schema to OpenDocument-v1.2 final version
> --------------------------------------------------------
>
> Key: ODFTOOLKIT-305
> URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-305
> Project: ODF Toolkit
> Issue Type: Improvement
> Components: odfdom
> Affects Versions: 0.8.8
> Reporter: Devin Han
> Assignee: Devin Han
> Labels: ODF1.2
>
> The final ODF 1.2 schemas were published last month, see:
> http://lists.oasis-open.org/archives/tc-announce/201201/msg00001.html
> And we just updated the code generator to support mainfest and data dignature
> element/attribute in issue ODFTOOLKIT-199.
> So I think it is time to update to the newest schemas for ODFDOM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
