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: reduced gate coverage and increased response times over US

Date: Fri, 23 Dec 2005 08:15:10 -0700
From: "Mark J. Nelson" <Mark dot J dot 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: reduced gate coverage and increased response times over US

Howdy, folks--

It's that time of year again, when the US sites shutdown for winter break, and Scott has officially urged us to "rest, recharge, reconnect and reflect."

All times/dates in this note are US/Pacific (PST) time zone.

Beginning NOW, Friday morning, December 23, the ON Nevada core team will be away from our desks.  None of us will be in the office.

We WILL be logging in sporadically, and we will respond to emergencies or problems as they are brought to our attention.  "How," you might ask, "do I bring something to your collective attention?"  The same way you always do: send e-mail to gk at onnv dot eng.  Then, if it's really an emergency and can't wait 24 hours for one of us to check in, CALL US.  Our work extensions are listed on http://onnv.eng/, and some of us even have our cell phones listed in namefinder.  Please try the work extension first, as many of us forward it as needed.

Traditional admonishment: the ON gate is a shared resource.  You are not the only one using it.  Be especially careful about ANY access to the gate during this time:

- Build lint
- Make sure that wx pbchk is happy
- Double check your parent gate setting BEFORE you bringover
- Build and test on every conceivably affected architecture
- Build lint
- Make sure that wx pbchk is happy

...or better yet: if you have no compelling reason to putback into build 31 (scheduled to close on Monday, January 2), WAIT.

As always, the consequences of your putback are your responsibility.  If you putback during this time, send us (gk at onnv dot eng) your contact info if you won't be monitoring your e-mail.  If you break something, we'll be unhappy.  If you break something and we can't contact you, we'll be downright angry.  And you probably wouldn't like us when we're angry...

So, negative stuff aside: if you need to work during this period, we will do our best to accommodate you.  Please be patient with us as we balance our family time with our work responsibilities.  If this is a time of celebration for you, then CELEBRATE!

See you in the New Year,

--Mark, on behalf of your ever-lovin' core team

PS Watch this space in January: Nevada Beta is fast approaching, and we'll need everybody to turn up their diligence by a notch or two...