IVLE 1.0rc2

Milestone information

William Grant
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon ivle-1.0rc2.tar.gz (md5, sig) IVLE 1.0rc2 source tarball 17
last downloaded 33 weeks ago
Total downloads: 17

Release notes 

This release does not have release notes.


View the full changelog

Features since 1.0rc1:
 - Cookies will be created with the 'secure' flag if served over HTTPS.
 - Admins can now create users through the web UI.
 - The user list now visibly separates users and admins, and indicates disabled users.

Bugs fixed since 1.0rc1:
 - A duplicate return link in exercise editor has been removed.
 - The help link in the file browser is no longer broken. This was a regression in 1.0rc1.
 - The console will now autoscroll earlier, hopefully eliminating some visual artifacts.
 - The Subversion diff and log functionality no longer crashes if credentials have not already been cached.
 - The environment variables passed to the server and Subversion diff and log services will now be minimal and correct, no longer inheriting critical values from the web server.
 - The value of the HOME environment variable in the console is now always correct. Previously it was in some circumstances the current working directory instead.

Documentation changes since 1.0rc1:
 - Installation from the Ubuntu package is now documented.
 - The upgrade process is now documented.
 - Tutor and lecturer privilege documentation has been updated and is now correct.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.