[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] RC5 ... are we done yet?

And EMF Teneo also has an issue which we discovered yesterday which impacts the modeling EPP.... I can do a new build today, hopefully in a few hours or less.

gr. Martin

Michael Spector wrote:
We have build problems with PDT, so RC5 is not ready yet.

On Thu, Jun 18, 2009 at 7:39 AM, David M Williams <david_williams@xxxxxxxxxx <mailto:david_williams@xxxxxxxxxx>> wrote:

    Yes, we are. Well, for staging site.
    Activity is quiet and no one has mentioned being delayed, so
    assuming we
    are done.
    And, just sort of done for sort of a short period of time.

    If someone really does have a true stop-ship bug, you can post re-spin
    request here for consideration to see if everyone else agrees to
    re-spin.
    (remember, it would have to be more than just a bad bug ... but
    something
    damaging to users or infrastructure).

    Now what?

    I know as we enter final daze
    http://wiki.eclipse.org/Galileo/Final_Daze
    (hint, read the document!)
    many people will eventually (over next week or two, depending on your
    releng processes) want to update your .build file to point to your
    "permanent" update site, instead of "milestones" or "interim",
    etc. That's
    fine, I'll leave builds "on" but these builds will not be pushed to
    'staging' (staging is done).

    That's fine, on one condition ... that you still make sure your .build
    file is correct and really "builds" ok. That's why we leave the
    builder
    active. We need to keep in a state of being able to re-build, in
    case it
    is needed for some reason. That's just good releng hygiene. It is
    harder,
    with Simultaneous Release, since the build "data" comes from two
    sources,
    the .build files (which we could tag, have control over, etc.) but
    also
    your own update sites, which totally depends on you and requires
    you to
    keep "constant" so we can always re-build, if we had to. And, don't
    forget, vice-versa ... if/when you change your "milestones"
    directory to
    "updates" (or similar) be sure you update your .build file so it
    will be
    accurate and continue to build.

    So, what next, after that?

    In about a month (or so) we'll start some maintenance efforts for
    Galileo
    SR1. At that point you'll update your .build files again (if you have
    maintenance) and provide an interim maintenance update site to
    pull from.
    But please do not modify your .build files for maintenance until
    instructed ... just to make sure we are all ready and know what's
    going
    on.

    As always, if questions, issues, or you need something special,
    just ask
    (here on cross-project list).



    _______________________________________________
    cross-project-issues-dev mailing list
    cross-project-issues-dev@xxxxxxxxxxx
    <mailto:cross-project-issues-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


------------------------------------------------------------------------

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxxxxxxxx - mtaal@xxxxxxxxx
Web: www.springsite.com - www.elver.org