Release notes for WeBWorK 2.0-pr3
The WeBWorK Team is pleased to announce the release of WeBWorK 2.0 Preview Release 3. While it is intended primarily for testing, development, and evaluation of the new system, it is also suitable for use in live courses.
This release includes almost all of the functionality of WeBWorK 1.9, and contains new functionality beyond what it possible with 1.9. New features since PreviewRelease2 include:
- improvements in speed and efficiency
- many user interface enhancements
- improved course creation procedure
- "remember me" cookie actually works
- installation documentation improvements
- many bug fixes
The complete system is distributed as two tarballs. One for the WeBWorK system itself, and one for the PG system, including a standard set of PG modules and macro files.
Files are available below and on our SourceForge project page:
Documentation on installing and configuring WeBWorK is available on this wiki. The relevant wiki topics are as follows:
- Installing Webwork
- Step 1: SystemRequirements - satisfy system requirements.
- Step 2: DirectorySetup - download and unpack the WeBWorK distribution.
- Step 3: ApacheSetup - configure apache.
- Step 4: TestCourse - create a test course to verify your installation.
- Step 5: SystemConfig - customize your system configuration.
- Step 6: MiscConfig - customize miscellaneous system-dependant settings.
- Creating and Upgrading Courses
- CourseCreation - creating a new course.
- CourseUpgrade - preparing a course from WeBWorK 1.x for use under WeBWorK 2.0.
If you need help installing or using WeBWorK 2.0, visit the WeBWorK discussion group and post your question there. The developers monitor this forum.
Bug Reports & Feature Requests
Submit bug reports and feature requests at http://bugs.webwork.rochester.edu/. We can't fix bugs and add features if you don't tell us about them!
While we welcome patches of any sort, by patching against the latest CVS code, you save us and yourself time. A bug in Preview Release 3 may be fixed in CVS, and we can more easily handle patches against the latest code. Check out the latest development version from CVS and patch against that. Consult the WeBWorKCVS topic for more information.
-- Main.SamHathaway - 14 Feb 2004 (Valentine's Day release, woo!)