[Fresco-devel] Draft of M2 Release Notes
aageorge <[email protected]> 10 Mar 2003 21:40:22 -0500
| Newsgroups | gmane.comp.video.fresco.devel |
|---|---|
| Message-ID | <1047350422.4179.86.camel@TheMachine> |
Hi, Here's a draft of the M2 release notes. Please poke, prod and comment on them. Any suggestions are welcome Regards, Allen -- aageorge <[email protected]>
Fresco-M2-Release-Notes
(text/plain, 1.8 KB)
Fresco M2 Release Notes
This is the second milestone release of Fresco. Fresco is a next-generation
windowing system based on a structured graphics toolkit of the same name.
It's goal is to use the vast body of research available to improve on current
windowing systems. Fresco has been designed with network/lanugauage
transparency, modularity, consistency and device independence in mind.
This release focuses on bug fixes, with the goal of improving server stabiliy.
In addition, it is the first step towards the goal of making regular releases
every few months.
Changes since M1:
Platform support
Fresco should now be built with gcc >= 3.2 only
Ported to FreeBSD -current
Ported to Solaris
Feedback is appreciated on how Fresco performs on the above platforms
Added Features
A new scenegraph debugging framework has been added
Bug Fixes
Python runtime works again
Improved server stability (Bugs 143, 158, 92, 9, 82, 188, 178, 153)
Development Infrastructure
Added vim, emacs and indent configurations to support new <a
href="http://http://www2.fresco.org/coding-style.html">coding
guidelines</a>
Get Fresco:
You can download M2 from our <a
href="http://download.fresco.org/releases.html">Releases Page</a>.
Contact Information:
If you have any questions about Fresco, feel free to catch us at #fresco on
irc.freenode.net. You can also subscribe to our <a
href="http://www2.fresco.org/mailinglists.html">Mailing lists</a>. You should
report bugs with our <a href="http://issues.fresco.org">Issue Tracker</a>.
You can also contribute by taking a look at some of our open issues for <a
href="http://issues.fresco.org/milestone3">Milestone 3</a> or at some of the
tasks/bugs in our Issue Tracker.