[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

X Strike Force X.Org X11 SVN commit: r927 - branches/modular

Author: dnusinow
Date: 2005-12-06 01:48:28 -0500 (Tue, 06 Dec 2005)
New Revision: 927

Add TODO list

Added: branches/modular/TODO
--- branches/modular/TODO	2005-12-06 06:25:38 UTC (rev 926)
+++ branches/modular/TODO	2005-12-06 06:48:28 UTC (rev 927)
@@ -0,0 +1,44 @@
+1) Get internal X.org utilities like mkfontdir building and working
+   properly. We don't have to organize these in to their proper packages
+   just yet, but it might be a good idea to at least start.
+2) Get the -common packages working. Daniel and I have discussed
+   trimmming them down to just xorg-common, and I have to investigate if
+   this is really feasible and worthwhile. Either way, we need to get
+   the packages that set up the symlinks working and building.
+3) The above seem to be the critical steps that I'm aware of right now
+   to get the full working server install building from our repo and
+   running in a chroot. Step 3 is to get any of the things I'm not aware
+   of in order to acieve this goal :-)
+4) Finish packaging the drivers. This should be trivial. If anyone wants
+   to package the ones they need to test the server on their systems,
+   please go for it! If you have any questions about how I've done
+   things so far, *please* ask.
+5) Package the apps. This involves deciding on the organization and
+   layout of the packages. Daniel has done a lot of this work already,
+   so we should look over what's in Ubuntu. As I understand it, Eugene
+   has also been thinking in this direction.
+6) Package any remaining data or other miscellaneous items we have lying
+   around.
+7) By this point we should be able to do a full, working install of the
+   X Window System. Make sure this is true, more or less.
+8) Get smooth upgrades working from both unstable and sarge. We can
+   steal liberally from the monolithic packages for this, since many of
+   the problems are already solved there. This should also include use
+   of piuparts to do automated checking of our work for us. Once this is
+   done, we should be ready to upload to unstable, but I'll be planning
+   on being flexible on the actual upload to unstable depending on where
+   we are.
+9) Port our patches from the monolith to the modular tree
+10) Q&A for etch. This includes a lot of the work from #8, but it also
+    includes extensive testing. Most of this should be done in
+    conjunction with the users of unstable and testing. I expect the vast
+    majority of the Q&A we do to be in this portion, rather than in #8.

Reply to: