Re: cvs, branches and co

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Fri Apr 04 2003 - 09:08:35 EST

  • Next message: Anders Peterson: "Re: cvs, branches and co"

    Hi,

    Am Freitag, 04.04.03 um 15:46 Uhr schrieb Christian Edward Gruber:

    > Dear Ulrich,
    >
    > Are you seriously telling me that eclipse can't handle a 1.0.10? Does
    > it automatically wrap to 1.1.0? That's just ridiculous!
    >
    You're right. There will be enough numbers for us. It's time for the
    weekend. :-)

    > As to Eclipse-versions, can we do something like
    >
    > Wolips_e210-1.0.6
    > Wolips-e220-1.0.6
    Very good idea. I'll add the eclipse version to the tar.gz. Any veto?
    When we support the Eclipse update mechanism this will be handled
    automatically.

    >
    > To the extent that we want to support multiple versions of eclipse with
    > a given plugin. Whatever the scheme, the goal of two versions of 1.0.6
    > that support different eclipse version co-existing on the update server
    > is pretty important, I should think.

    Another question is when we should start to build against 2.2.0?

    >
    > Regards,
    > Christian.
    >
    >
    >> -----Original Message-----
    >> From: Ulrich Köster [mailto:ulric..bjectstyle.org]
    >> Sent: Friday, April 04, 2003 4:41 AM
    >> To: woproject-de..bjectstyle.org
    >> Subject: cvs, branches and co
    >>
    >> Hi,
    >>
    >> there were some private discussion about branches. The target is to
    >> have multible branches for the different releases like 1.0.0 and
    > 2.0.0.
    >>
    >> Some things to we should talk about:
    >>
    >> - How to match with the Eclipse version system? Let`s assume we have
    >> two branches 1.0.0 and 1.1.0. After a while there will be a bugfix
    >> release for 1.0.0 named 1.0.1. Looks good. But what if we update a
    >> plugin name org.objectstyle.cayenne_1.0.6 from version beta3 to beta4.
    >> The Eclipse update facillity will not recognize that
    >> org.objectstyle.cayenne_1.0.6 has changed. This is not a problem when
    >> we provide the dist as a tar.gz but for the 1click update within
    >> Eclipse this is a problem. Features are another problem. If we
    >> increment the version of one plugin we need to increment the version
    >> feature. I is very likely that a feature with version and branch 1.0.0
    >> with many plugins exceed it's 1.0.9 limit if there is allready a
    > branch
    >> 1.1.0 or the head is 1.1.0 .
    >>
    >> - Directory layout: If we talk about branches we should also talk
    > about
    >> the directory layout.
    >>
    >> cvsroot -> wo
    >> -> build.xml The buildscript to build
    > all.
    >> -> build A folder with
    > build scripts. For
    >> instance to build a
    >> plugin or feature.
    >> -> woproject woproject stuff with
    > build.xml
    >> -> wolips wolips stuff
    > with build.xml
    >> -> xdocs homepage
    >>
    >>
    >> Ulrich
    >
    >



    This archive was generated by hypermail 2.0.0 : Fri Apr 04 2003 - 09:13:23 EST