PSARC/2007/600

The Ruby PSARC case got approved quite speedily. It could have been all the prior research into compatibility, file layouts, directory structure done(in response to a lot of good questions from Jyri).

Or it was probably because you hear that the ARCs are a source of delays, and other such scary rumors, so that when you really go through it, and realize that it's not true, you're confused.

MySQL was the other ARC case that seemed to sail through.
So, I'm going to dismiss perceptions of ARC tardiness as fiction(at least in my limited experiences).

My advise to anyone who wants to write an ARC case for OpenSolaris:

-> Read prior ARC cases to get a feel for how they're written(ie., the tone).

-> Think Interfaces, Interfaces, and Interfaces. ie., what interfaces does your software expose, what does it expect? What's the stability of each of these interfaces?

-> Look for precedence. ie., If you're proposing the addition of a new scripting language(like Ruby), look for older cases where scripting languages were approved(like Perl).

-> Think about compatibility/stability across versions. Across what releases is compatibility guaranteed? Across which releases is backward compatibility broken? What constitutes a stable release? What constitutes a development release?

Solaris is all about backward compatibility and stability.

-> And give this research a lot of time - otherwise, you're tempted to cut corners, and somehow wing your case. This impulse is detrimental to Solaris - which is the software you're trying to improve by making an ARC proposal in the first place.

Well, that's enough rambling about ARC cases, I've got to ease into my week end Martinis :-)

Cheers!

Comments:

Post a Comment:
Comments are closed for this entry.
About

prashant

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today