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 : Sat Apr 05 2003 - 10:51:18 EST