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. Build 101-105
      3. Builds 96-100
      4. Builds 91-95
      5. Builds 86-90
      6. Builds 81-85
      7. Builds 76-80
      8. Builds 71-75
      9. Builds 66-70
      10. Builds 61-65
      11. Builds 56-60
      12. Builds 51-55
      13. Builds 46-50
      14. Builds 41-45
      15. Builds 36-40
      16. Builds 31-35
      17. Builds 26-30
      18. 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: ON Nevada gate now open

Date: Mon, 11 Aug 2008 14:28:06 -0600
From: "Mark J. Nelson" <Mark.J.Nelson at sun dot com>
To: on-discuss at opensolaris dot org
Subject: Heads up: ON Nevada gate now open


...and GO!

OK, we're removing the provisional restriction, you may now push at will.

Of course you will still need to have an approved RTI.

And please (per the tools flag day note [1]) make sure you're using the 
latest SUNWonbld.  That's important because it will disable keyboard 
interrupts in your terminal session, so you won't be able to do a silent 
push (ie one that doesn't generate notification e-mail).  If you manage to 
do this anyway (ie interrupt a push), don't panic: see the next paragraph.

If you see errors in the output of your push command, please copy and 
paste them into either an e-mail or pastebin [2], and send them to 
gatekeeper at onnv dot eng dot sun dot com.

Regarding ssh keys [3]: we are now updating the authorized keys once per 
weekday, at (or slightly after) 9:00AM Mountain Time (except for today, 
where we just got 'em a few minutes ago).  If you create or change an ssh 
key on opensolaris.org, it will be authorized the next morning.

And because I can't help it, and I tend to repeat myself: you'll need to 
sync with the clone:

 	hg pull ssh://onnv.sfbay//export/onnv-clone

...and merge:

 	hg merge

...and commit the merge:

 	hg commit -m "merged updates from onnv-clone"

...and recommit:

 	hg recommit

before you can successfully push to the gate:

 	hg push ssh://onhg at onnv dot sfbay//export/onnv-gate

If you've done all of that, and you still encounter problems, you may 
contact us at gatekeeper at onnv dot eng dot sun dot com, or visit us in IRC at 
SunIRC/#hg-help.

--Mark

[1] http://www.opensolaris.org/os/community/on/flag-days/pages/2008080701/
[2] http://paste.east/
[3] http://www.opensolaris.org/os/community/on/flag-days/pages/2008080404/



On Fri, 8 Aug 2008, Mark J. Nelson wrote:

> Date: Fri, 08 Aug 2008 17:27:18 -0600
> From: Mark J. Nelson <Mark.J.Nelson at Sun dot COM>
> To: on-discuss at opensolaris dot org
> Subject: Heads up: ON Nevada gate opened (provisionally)
> 
>
> The ON Nevada gate is now provisionally opened for push.
>
> What does that mean?  It means that we have (intentionally) not yet added all 
> of the ssh keys to the list of authorized users.
>
> If you're ready to push, we're ready for you, but you'll need to follow these 
> steps:
>
> 1. Make sure you're in sync with the onnv-clone, so that you won't need to 
> pull/merge/recommit.
>
> 2. Send e-mail to gk at onnv dot eng dot sun dot com and say "I'm ready to push."  In that 
> e-mail, please include either your opensolaris userid, or attach your public 
> ssh key as a separate file.
>
> 3. Wait for one of us to reply and say "ok, go ahead."
>
> Why are we doing it this way?  So that we can be sure that one of us is 
> paying attention, in case we need to ask or answer questions, and so that we 
> can check up on how things are running.
>
> On your marks, get set....
>
> --Mark
>