Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Status and outlook for RC1 stagingrepo ... 10 AM Thursday?

Hi Team,

All the projects I produce builds for and contribute to Helios were "mostly late". Excuses here

Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager
IBM Rational Software: Aurora / Modeling Tools
Phone: 613-270-4613

Inactive hide details for "Oberhuber, Martin" ---2010/05/20 12:46:25 PM---Greg,"Oberhuber, Martin" ---2010/05/20 12:46:25 PM---Greg,


"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>


"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>


2010/05/20 12:46 PM


RE: [cross-project-issues-dev] Status and outlook for RC1 stagingrepo ... 10 AM Thursday?


to be very clear: A TM RC1 build has not been made and never publicly announced.
TM RC1 == TM M7.

I did play with the thought of contributing a late RC1 yesterday, and actually
performed a build which includes 5 fixes of which 3 were made after the
official RC1 cutoff. But since there was not enough time for testing everything,
I preferred keeping things as they are.

I'm sorry if this caused confusion.

Martin Oberhuber, Senior Member of Technical Staff, Wind River
direct +43.662.457915.85 fax +43.662.457915.6

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Watson
Thursday, May 20, 2010 1:11 PM
Cross project issues
Re: [cross-project-issues-dev] Status and outlook for RC1 stagingrepo ... 10 AM Thursday?

We have not been able to build against all RC1 components because DSDP TM only completed their RC1+1 build this morning. Given that some projects are this late I think it's reasonable to allow dependent projects some extra time to do their build.


On May 20, 2010, at 3:50 AM, Markus Knauer wrote:
      10 AM (Eastern) for the staging repository - if there is a small problem/error it will cause a delay, but I am confident that it can be done...

      10am - 11.30am -> time frame for building the EPP repo
      11.30am +++ -> build the final packages, package maintainer can test and sign off immediately when their package drops out of the build

      Friday 1am -> copy the packages to the mirrors
      Friday XX pm -> enable package download for all packages that received a "+1" until then

      The consequence of this is (but that is no difference to the last milestones) that a "-1" vote of a package results in disabling it on Friday's release. If possible I would try to fix such a "-1" package, rebuild it and add it some time next week to the download packages, but that needs to be decided as the case arises.

      Thanks and regards, Markus

      On 20 May 2010 07:42, David M Williams <david_williams@xxxxxxxxxx> wrote:

        Late again? A little.

        There is a fairly final /releases/staging repository, but has a few problems:

        1) I had to remove teneo, since it was failing in a way that would fail whole build .... and Martin Taal contacted me right before I went to bed :) saying he thinks he has it fixed and has started a rebuild.

        2) Riena has a bad pack.gz file, so its set of bundles are incomplete. Christian Campo is actively looking into it .. but he just got up :)

        3) And ... I just noticed from hudson log ... a new (late) contribution from MPC!?: bug 308687: [releng] include MPC contribution

        So, I'm willing to check in morning, and promote one more ... if everything is perfectly successful. Otherwise, we'll have an RC1 with what we have right now and ... well, we'll see how it looks Thursday morning.

        I'll set 10 AM (Eastern) as a hard cut-off ... we will be done by then, one way or the other. Oh ... and no one else please use this as an excuse to add some new build/fixes. If your building now, leave it alone and
        don't risk breaking anything.

        If anyone (Markus?) has any concerns with this slightly extended deadline, please just say so. I personally am fine with what we have.

        And, team, let's please put the "simultaneous" back in simultaneous release, and everyone be on time next week. Or, at least, _you_ write the long note like this one to cross-project explaining why you are late.

        Thanks all,

        cross-project-issues-dev mailing list


      cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

GIF image

GIF image

Back to the top