harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov" <alexey.v.varla...@gmail.com>
Subject Re: [snapshot] Freezing the code for Milestone build?
Date Thu, 26 Apr 2007 12:30:25 GMT
2007/4/26, Alexey Petrenko <alexey.a.petrenko@gmail.com>:
> CC reports no failures for x86 now.
This is intermittent failure...
>
> 2007/4/26, Alexey Petrenko <alexey.a.petrenko@gmail.com>:
> > It looks like I've missed drlvm-test failure on Windows/x86. Are
> > somebody from VM gurus looking into?
> >
> > SY, Alexey
> >
> > 2007/4/26, Alexey Petrenko <alexey.a.petrenko@gmail.com>:
> > > Now means now. I see number success alerts from CC and all the x86 CCs
> > > looks up on the mentioned page.
> > >
> > > Did I miss something?
> > >
> > > SY, Alexey
> > >
> > > 2007/4/26, Mikhail Loenko <mloenko@gmail.com>:
> > > > 2007/4/26, Alexey Petrenko <alexey.a.petrenko@gmail.com>:
> > > > > Looks like all the CCs are up now. Is that correct?
> > > >
> > > > the 'now' is last time you pressed 'refresh' :)
> > > > what does 'now' mean in your case?
> > > >
> > > > Thanks,
> > > > Mikhail
> > > >
> > > > >
> > > > > SY, Alexey
> > > > >
> > > > > 2007/4/26, Mikhail Loenko <mloenko@gmail.com>:
> > > > > > We should freeze when all CCs are in the up state [1]
> > > > > >
> > > > > > Can we use the snapshots [2]? My understanding is that the snapshots
> > > > > > are updated in the "all CCs up" moments, so probably almost-a-week
old
> > > > > > snapshots are the best for the Milestone.
> > > > > >
> > > > > > Were there any significant changes since that? I know about
gc switch,
> > > > > > but not sure how it affected stability...
> > > > > >
> > > > > > Thanks,
> > > > > > Mikhail
> > > > > >
> > > > > > [1] http://www.harmonytest.org/upload/cc1.html
> > > > > > [2] http://people.apache.org/builds/harmony/snapshots/
> > > > > >
> > > > > > 2007/4/26, Tim Ellison <t.p.ellison@gmail.com>:
> > > > > > > To ensure we get a stable build we need to freeze the code
for a short
> > > > > > > duration, which will allow us to:
> > > > > > >
> > > > > > >  - produce the set of milestone candidates,
> > > > > > >   i.e. a full rebuild on Windows, Linux (with libstdc++
v5 dependency)
> > > > > > >   and Linux (with libstdc++ v6 dependency) in JRE, JDK,
and HDK
> > > > > > >   formats.  At this point we will still only publish x86
snapshots.
> > > > > > >
> > > > > > >  - test the snapshots,
> > > > > > >   i.e. test installs (it would be good if you have a machine
without
> > > > > > >   your usual development environment set up to ensure we
don't have
> > > > > > >   dependencies on dev tools); and testing various applications
to check
> > > > > > >   they work as well as we would expect for this snapshot.
> > > > > > >
> > > > > > > While we do this it is helpful if the codebase is not being
changed.  It
> > > > > > > sounds like people are happy enough to freeze HEAD rather
than create a
> > > > > > > branch, so let's do that.
> > > > > > >
> > > > > > > During the freeze there should be no commits unless we
agree here on the
> > > > > > > dev list that there is a problem serious enough for us
to re-spin a new
> > > > > > > candidate.  I would hope that producing the snapshots and
some focused
> > > > > > > testing can happen over one or two days (max) to declare
the build good.
> > > > > > >  Once the milestone is declared good we will reopen for
development as
> > > > > > > usual.
> > > > > > >
> > > > > > > Does that sound like a reasonable procedure?  Did I miss
anything out?
> > > > > > >
> > > > > > > so:
> > > > > > >  - when do we freeze (today/tomorrow)? any outstanding
MUST fix's?
> > > > > > >  - volunteers with machines for producing the candidates?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Tim
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Mime
View raw message