Maintain news

The Maintain demo site is now up and running at:

http://maintaindemo.osuosl.org/

Feel free to login with username demo and password maintain3 and try it out. You can report any bugs you find at our Bug Tracker. (You'll need to register to report bugs.)

The newest version of Maintain, version 3.1.1, has been released!  The project is currently alive and in development.

To find out more about this release, read the release notes.  It can be found in the downloads section of the site.

For any questions or comments, feel free to stop by on IRC or leave a note in the forums.

We got together and cleaned up our bug tracker, which can be found at http://bugs.osuosl.org/

The 2.x series of releases are archived, so issues can no longer be filed under those versions of Maintain.  All the releases previous to 3.1 have been marked as released, so while bugs can still be filed under these versions no new features will be added to these versions.  Also, all bugs that require major rewriting will be fixed in the newer releases.

Currently, any issues found in the most recent version of Maintain should be filed under version 3.1.

Here is our current roadmap of Maintain: http://wiki.osuosl.org/display/Maintain/Maintain+Project+Roadmap

The newest version of Maintain, Maintain 3.1.0, has been released!

This version is released under the new version system for Maintian3. All versions with an even digit in the second place are stable, and all digits with an odd digit in the second place are unstable. That is to say, when 3.1.x is stable it will be released as 3.2.0, and an unstable version 3.3.x will be released when new features are added, only bug fixes will be added to 3.2.x from that point on.

Maintain 3.1.0 is our first unstable release under our new version system; keep in mind that this means that this software has not yet been as extensively debugged as a stable release. Please read the release notes for more information about 3.1.0.

For any questions or comments, feel free to step by on IRC or leave a note in the forums

For users and developers equally, we added two new featured documents to the documentation wiki:

The Maintain FAQ gives an overview of the most frequently asked questions about Maintain so far. If you have additional questions not covered in the FAQ, please feel free to contact us or leave a note in the forums. We'd be happy to answer it and if it is interesting for other people, too, we will likely add it to the FAQ eventually.

If you want to extend Maintain as a module writer, the new Module Writing Guide is a good point to start. It explains the basics of how modules work and how you can start to make your own module.

Good luck!

Update: We also added a little tour through the Maintain Backend for developers.

We have added a Maintain Code Contribution Guide to the constantly growing Maintain documentation!

If you want to contribute code to the Maintain project, these are some simple guidelines you need to follow.

Along with the contribution guide, we published a Laundry List on the wiki containing ideas for modules etc., if you want to help us but don't quite know where to start.

A big thanks to all current contributors and welcome to the ones planning to join us!

By the way: There are more howtos etc. in the works and will be published here when they are done. Stay tuned!

Approximately two weeks after the Maintain 3.0.0, RC 1 was released, we are proud to announce the second release candidate.

A lot of bugs could be fixed, and Maintain is on the way to its stable 3.0.0 release. Please read the release notes for more information about RC2.

For any questions or comments, feel free to step by on IRC or leave a note in the forums.

After intensive redesigning, simplifying, and extending the Maintain network management software, the Maintain team is proud to announce the release of

Maintain 3.0, Release Candidate 1!

Feel free to download this version, install it on a test environment and see if it fits your needs.

Please stay in close contact with us so we can learn about possible improvements of our software. Your feedback is important to fix as many bugs as possible before the release of the final version!