OpenSolaris

heads up: restrictions on builds 110 and 111

Date: Wed, 04 Feb 2009 19:04:26 -0800
From: John Beck <jbeck at eng dot sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com
Subject: heads up: restrictions on builds 110 and 111

Howdy gatelings,

As shown on the ON Nevada build schedule [1], the content of builds 110
and 111 will be partially restricted to stabilize the OpenSolaris 2009.06
release.  Note that this is a change from my earlier announcement [2], and
shorter notice than we usually provide.  However, as Vincent's announcement
earlier today [3] suggested, Sun's recent reduction in force has had an
impact on our plans.  Note also that this schedule is tentative, subject
to confirmation in the near future.

Here are some guidelines on how we approach such milestone builds, and ON
CRT (change review team) advocacy in general:

* use good judgement

  Not all bugs and RFEs are equally important.  If you are headed for
  integration into a restricted build, consider delaying until after the
  restriction has been lifted.  The goal of restricted builds is stability
  and bug reduction, not new features.  Expect your CRT Advocate to discuss
  this with you if you file an RTI during the restricted period.

* shrink to fit

  All of our processes are designed to shrink to fit the occasion.  If a
  given change is low risk, low impact, and high reward, then it needs less
  scrutiny.  Things that are higher risk, higher impact, or lower reward
  will receive more attention, especially during restricted builds.

* milestone builds

  Traditionally, we have clamped down on milestone builds.  But in this
  era of regular (more or less semi-annual) milestones, the following seems
  appropriate (in this case, N=111):

  * N-2: no restrictions
  * N-1: RFEs and bug fixes that are low-impact
  * N: RFEs and bug fixes that are low-impact and low-risk
  * N+1: no restrictions

* code reviewers

  We have often required two code reviewers for milestone builds in the
  past.  This, however, also falls under the above points about good
  judgement and shrink-to-fit.  So two (or more) reviewers are recommended
  for milestone builds, and also for a high-risk or high-impact change at
  any other time.

If you think an RTI's risk or impact might be too high, and you missed the
last unrestricted build (109 in this case) before the milestone in question,
defer it until the next unrestricted build (112 in this case).  When in
doubt, consult the tech lead (i.e., me at present).

~-- John

[1] http://opensolaris.org/os/community/on/schedule/
[2] http://mail.opensolaris.org/pipermail/on-discuss/2008-December/000498.html
[3] http://mail.opensolaris.org/pipermail/opensolaris-announce/2009-February/002031.html

{{{_______________________________________________}}}

on-discuss mailing list
on-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/on-discuss