OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads up: two code reviewers for builds 63/64

Date: Mon, 02 Apr 2007 15:50:23 -0600
From: "Mark J. Nelson" <Mark.J.Nelson at Sun dot COM>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at Sun dot COM
Subject: Heads up: two code reviewers for builds 63/64


I added the "heads up," which I think will make this visible on 
OpenSolaris.  At least that's my intention.

Anyway, reminder text below.  We start snv_63 after tonight's clone update 
(23:00 PDT).

--Mark

> The next Solaris Express Developer Edition release will be based on the best 
> of two builds (snv_63 and snv_64).
>
> Because we won't be forking or restricting builds, starting in build 63, 
> please:
>
> Gatelings: be extra careful with your changes, and get at least two subject 
> matter experts to code review them.
>
> CRT Advocates: please pay extra attention to how thoroughly changes have been 
> tested, and enforce the two code reviewers rule.
>
> No need to reassign RTIs to me during these builds, but you certainly may if 
> you desire.