Nils Nieuwejaar wrote:
On Tue 02/28/06 at 10:16 AM, [EMAIL PROTECTED] wrote:
Yup, I should be able to deliver it today. Though, while you're all
waiting eagerly in anticipation, might I suggest reading this:
http://whacked.net/2006/02/28/when-a-nightly-that-closes-on-a-build-date-isnt-a-build/
to explain why a nightly sync that closes on a build date isn't always a
build.
The big problem for me (and isn't that what really matters?) is that this
complicates the BrandZ/Xen release mechanism.
If your code drop is out of sync with the official build snapshots we base
our releases on, the OpenSolaris binary components may be out of sync as
well. This would require both teams to start delivering our own binary
wads. I'm sure that would be possible, but we would need some instructions
on how a distributable binary wad is constructed.
I'm happy to give instructions on how to create the closed-bins, but I
agree - it's silly for both of us to deliver these.
Alternatively, we could base our releases on the OpenSolaris source tree
rather than on the final snapshot tree. To make that work, we would just
need you to give us a pointer to the full teamware workspace you base your
release on. If you could set up an opensolaris-snapshot archive that holds
the full teamware workspaces for each of your weekly releases, that would
be perfect.
I keep my Teamware workspaces for at least the past 3 deliveries around
on stomper.sfbay currently (/export6/stevel/tonic.[date]). Would those
suffice? How often do you guys make deliveries?
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
opensolaris-discuss mailing list
[email protected]
