incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daisy Guo <daisy.yc...@gmail.com>
Subject Re: Confirm the change set will be included in the first release.
Date Mon, 26 Sep 2011 07:51:08 GMT
2011/9/23 Svante Schubert <svante.schubert@gmail.com>:
> Am 23.09.2011 01:16, schrieb Rob Weir:
>> On Thu, Sep 22, 2011 at 2:57 PM, Svante Schubert
>> <svante.schubert@gmail.com> wrote:
>>> Am 22.09.2011 19:17, schrieb Rob Weir:
>> <snip>
>>
>>>> 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.
>>>
>> I like the idea of tracking versions at the component level as well as
>> for the combined release.  But I don't see the logic behind calling
>> the initial Apache release 0.8.7.  How about just starting simple, and
>> calling the whole thing 0.1?
>>
> No objection to 0.1 for the combined release, I thought you would
> objected it ;)
>
+0

Mime
View raw message