Hi Rob,

Initially when a build closes there is nothing different between the build
and the nightly build done on the same day except some strings so
`uname -a` reports "snv_X" instead of the date it was built.

When a build closes we send off packages to PIT which does regression
testing for about a week. During the course of their testing they may find
a problem that makes the build unusable. So we "respin" the build.

That is a process where the ON gatekeepers (me or Suha) take a bug fix
and pull it into the build snapshot. We then rebuild it and if there is time
send that back to PIT. These iterations happen up to the time we have to
deliver the build to Release Engineering (RE). RE has additional tests
they do after all the consolidations deliver their packages. If for example
the build didn't boot on sparc some consolidation has to respin again,
possibly ON.

But eventually we get something stable enough to be used. At that point
snv_X may or may not be the same as the nightly build on the day
build X closed.

This is also why builds show up long after they have closed on the
download center. They aren't put on the download center until the
weekend after RE has made the build available. In general, I was late
making b80 available.

So the download center has a few places you can go:
    http://dlc.sun.com/osol/on/downloads/bX
    http://dlc.sun.com/osol/on/downloads/current
    http://dlc.sun.com/osol/on/downloads/nightly-bins

As you pointed out http://dlc.sun.com/osol/on/downloads/20080107
(which is "current" right now) is what build 81 is going to be based
off of. How much will build 81 differ? I know there is at least one
respin that will happen. But in general I can't answer that question.
I don't know until PIT finds a problem if there will be a respin.

I'm not sure what you mean by the "snv_xx changeset". There is
already a build 79a. And there will be a build 79b too probably.
The 'a' and 'b' builds for SXDE haven't been put up on the DLC.

The nightly-bins *should* be updated daily. They used to run out
of `cron` but were slowing down all the other builds the gate was
doing. So now they are started by hand after the gate is BFU-ed.
It would be nice to only provide updated closed bins when they
actually change. But since a header file in usr/src can be included
in closed source files it really isn't easy to know when. So the
default has been daily.

-dvd


> ------------------------------------------------------------------------
>
> Subject:
> [on-discuss] workflow
> From:
> Rob Logan <Rob at Logan.com>
> Date:
> Thu, 10 Jan 2008 01:55:36 -0500
> To:
> on-discuss at opensolaris.org
>
> To:
> on-discuss at opensolaris.org
>
>
> could someone describe the on build differences?
>
> mainly what separates snv_80
> http://www.opensolaris.org/os/community/on/schedule/
> currently
> http://dlc.sun.com/osol/on/downloads/b80/on-changelog-b80.sparse.txt
>
> and the opensol-20080107-nd builds, currently
> http://dlc.sun.com/osol/on/downloads/20080107/on-changelog-20080107.sparse.txt
>
> how much will opensol-20080107-nd differ from snv_81
> when it contains the changeset?
>
> how often is the snv_xx changeset modified when the SXDE is
> assembled? (I seem to recall a snv_70a or something)?
>
>                       Rob
>
>   

Reply via email to