I'm not sure I understand...
Will there be two separate series of version numbers and tags - one for
builds and one for releases?
Everytime we build we tag CVS with a serial number (and date).
The WOLips version exposed to Eclipse will be the same for several
builds, and has nothing to do with the build number. Just like we've
been using WOLips 1.0.0 for a while now.
A release is made when/if the build works as expected, and there is a
CVS tag/branch for every released version.
Is that what you meant?
On söndag, apr 6, 2003, at 17:36 Europe/Stockholm, Ulrich Köster wrote:
> Hi,
>
> the buildserver can increment a version with every build and tag the
> cvs. It should be easy to add some lines to the build script to
> maintain a file (.html) with a list of tags and dates.
>
> Example
>
> 1 5.1.2003
Is this january or may?
/Anders
> 2 5.2.2003
> 3 5.3.2002
> .
> .
> .
>
>
> Version 1.0.1 may be build 36 from 6.8.2003.
>
> To keep it simple for us we should keep WOLips compatible with
> different Eclipse versions rather than maintaining different branches
> for it.
>
> Ulrich
>
> Am Samstag, 05.04.03 um 17:46 Uhr schrieb Anders Peterson:
>
>> Hi,
>>
>> The important thing is that automatic builds have timestamps, and
>> (manual) releases have version numbers. My guess is that
>> tags/versions in CVS only exist for releases. (It is possible to
>> check out from CVS based on a timestamp.)
>>
>> Regarding support for multiple Eclipse versions "_e2.3.0_". Do we
>> know which problem we're trying to solve?
>>
>> How is the difference between WOLips_e2.1_1.2.3.tar.gz and
>> WOLips_e2.2_1.2.3.tar.gz made? Is it with different build script
>> targets, or with different branches in CVS? Perhaps both.
>>
>> Will there actually be versions of WOLips (same version number, same
>> CVS tag) supporting different incompatible Eclipse versions?
>>
>> If Eclipse 2.2 is incompatible with 2.1 couldn't we just say that
>> WOLips 2.y.z is for Eclipse 2.2.z and WOLips 1.y.z is for Eclipse
>> 2.1.z? We would already have a branch separating WOLips 1.y.z from
>> 2.y.z.
>>
>> /Anders
>>
>> On fredag, apr 4, 2003, at 18:50 Europe/Stockholm, Ulrich Köster
>> wrote:
>>
>>> Hi,
>>>
>>> we could enhance it. Andrus has offered us the horsepower from
>>> www.objectstyle.org. We can use it for anthill to provide nightly or
>>> weekly builds. This progress could also be used to run the unit >>
>>> tests.
>>>
>>>
>>> If I get it right, we need the following distributions/versions:
>>>
>>> Developers:
>>> Nightly builds with build IDs. WOLips_01.01.2004_e2.3.0_2.1.3.tar.gz
>>> Build from source.
>>>
>>> User:
>>> Releases available via update or download. WOLips_e2.3.0_2.1.3.tar.gz
>>>
>>> Testers and early adopters have access to both.
>>>
>>>
>>> Ulrich
>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Mon Apr 07 2003 - 13:49:42 EDT