incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Devin Han <>
Subject Re: Confirm the change set will be included in the first release.
Date Fri, 23 Sep 2011 03:48:28 GMT
2011/9/23 Svante Schubert <>

> Am 22.09.2011 19:17, schrieb Rob Weir:


> > What we can do now, is make progress in areas like:
> >
> > 1) A script to build the combined release archives for the project
> +1

> >
> > 2) Drafting combined release notes, or maybe a top level release note
> > that points to component-specific release notes?
> I would love to have an introduction of the overall purpose and the
> modules we are offering. Like someone would have for an SDK...
> Regarding the release notes, I like your idea of having one collected
> summary and references to the detailed distinct release notes.

> >
> > 3) Maybe unified JavaDoc?
> I really do like the easiness of the Simple API JavaDoc as there are so
> little classes involved.
> We should only give the user the complexity, he needs. Therefore I
> prefer to have distinct APIs for the distinct modules.
> >
> > 4) Merge of ODFDOM and Simple API could also be done, I think.  Or
> > next release.  I don't have strong preference.
> Quoting you from above:
> > "I'd support the idea of making an Apache release of the code we have
> > now, doing the work necessary to meet the Apache requirements, but not
> > making any functional changes to the code."
> I would drop the Simple API / ODFDOM DOC merge for the first release.
> Especially as we should keep Simple API as its own distinct bundle to
> maintain the simplicity, as users might want to work solely with that
> high level API.
> I am curious how a merge might look like, does anyone of the former
> Simple API team have suggestions?
I suggest remove the ODFDOM Doc layer at least. We haven't support it for a
long time. Many bugs in it, for example memory leak.
So we have to avoid new user use it and replaced it with Simple API.

> >
> > 5) We need to agree on an initial version number for the release.
> > Apache ODF Toolkit version X.X ?
> Currently every module ODF Validator, ODFDOM and Simple API has its own
> version number. (Michael Brauer - the former project owner - had not
> given a version number to the validator, but I added one with the recent
> update).
> The versions are now:
> 0.6.6. for Simple API
> 0.8.7 for ODFDOM and the validator.
> Does it makes sense to give each module its version number and a
> different one for the overall umbrella deliverable?
> I think this make sense as if there are new tools in the future, they
> might start with their own numbering and if a module was not change its
> version will not be updated, otherwise confusing the user.
> Therefore my suggestion is to keep the version numbers of all sub
> projects and give the overall project the highest version number of all
> for the start, 0.8.7.
> - Svante


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message