X.Org Community & OpenSolaris X release plans
By Alanc-Oracle on Sep 04, 2005
I had to write up a proposal recently for releasing the source from the X Window System consolidation  in Solaris to the OpenSolaris program, based on the ideas we had discussed in the X group and with our management chain for how to handle this. It's a sizeable writeup, so it follows a bit later in this blog entry. There's a problem with the schedule I prepared as part of this plan though - it was based on the X.Org Community Release Plans, which called for Xorg 6.9/7.0 to be released on this approximate schedule:
- XX Aug 2005: Release Candidate 1 (features & bug fixes)
- XX Sep 2005: Release Candidate 2 (bug fixes only)
- XX Sep 2005: Release Candidate final (critical bug fixes only)
- XX Oct 2005: X11R6.9/X11R7 Release (Documentation changes only)
In the past we've found that the Release Candidate 1 phase is about the same quality as our integration criteria for Solaris - features finished, major bugs fixed, documentation mostly done except for some cleanup work - and so we've integrated those into our builds for testing, to help find problems early, hopefully in time so they can be fixed in the final release from the community as well as in our release.
Unfortunately, as you may have noticed, it's now September and the RC1 release hasn't come out yet from X.Org. The X.Org release managers recently posted a message on this to the Xorg mailing list with details on what needs to be finished before the RC1 release can happen. There's a number of ways interested people can help to get the Xorg community releases ready for all platforms, and for those who want to see the Solaris X sources released via OpenSolaris, helping with that is the best way to help our release plans move forward too. Ways you can help include:
- Building all the 7.0 modules and reporting any problems you find. Add configure.ac tests to replace any of the old Imake options or platform definitions.
- Setting up a tinderbox to continually build on a specific platform, so we can find out as soon as possible if a change breaks the build on that platform.
- Looking through the documentation to see what needs to be updated, especially because of the modularization/autotooling project.
- Testing bugs in the Xorg products in freedesktop.org bugzilla to see if they're still reproducible with the latest code from CVS
- Testing the proposed EXA patches for your hardware (if there are any yet) and reporting any bugs you find to the authors.
The xorg mailing list on freedesktop.org is the best place to ask if you have any questions about this. (If you try mailing me directly or responding here, don't expect a quick response, since I'm going to be out all week, and may not be near net much.)
So, remembering that the dates are probably slipping a few weeks, and that this is still just a proposal and not yet the fully approved plan, so still subject to change, here's the draft of our X for OpenSolaris release plans (slightly abridged for public release):
 For those not familiar with the Solaris terms, a "consolidation" is a set of related software packages built and integrated into the OS together. The initial OpenSolaris release was from the "OS/Networking", or "ON", consolidation, consisting of the kernel and core utilities. I work on the Solaris X Window System consolidation, usually known as "X" for short, which consists of the software you'ld find in the X.Org tree, plus similar custom software from Sun. It does not include CDE/Motif, JDS, or the Xsun graphics card modules, which all come from their own consolidations.
 Solaris fans should note that there's only two OS'es listed as fully supported in the modular release, and our favorite OS is one of them! Fans of other OS'es should note this is mainly because Sun's X engineering group is putting in the time to make this happen, and all you need to do to add your OS to the list is to respond to the call for volunteers to help out on other OS'es. Some work has been put in towards supporting the various BSD flavors, CygWin, and MacOS X, but not enough to be ready to claim full support yet.