superunstable

From: Mike Schrag (mschra..dimension.com)
Date: Tue Jan 29 2008 - 12:31:58 EST

  • Next message: Jeremy Matthews: "Re: superunstable"

    I'm contemplating the following:

    * Leave stable where it is for right now
    * Stop the nightly updates of "nightly"
    * Make a new "superunstable" folder that nightly builds build into
    * Commit the new classpath stuff
    * Sit back and watch the explosions

    I believe it is working OK inside of Eclipse (and I have a good handle
    on fixing anything that comes up), but my big concern is the build.xml
    files. There were fairly significant changes made, and it's really
    hard to know what CRAZY stuff people are doing inside their build.xml
    files, and I'm pretty confident there are going to be problems with it
    (did I mention I really hate ant?).

    The complication with this particular change is that there are people
    still using 4118 on stable, and there are people now using "nightly"
    as a "stable" for the new Eclipse/Leopard, so we have to have a REAL
    unstable place so that people who really want to try the broken stuff
    can do so while not breaking the other people even more in the meantime.

    Thoughts?

    ms



    This archive was generated by hypermail 2.0.0 : Tue Jan 29 2008 - 12:33:21 EST