Bugs found in v0.1.0-RC1

• Login will not work unless $conf['allowsavepwd'] = true is set in config.php
• When creating groups, you will first need to save the group name/description, before reloading the new group and adding users.
• Several different notice errors if you had error reporting turned on for Notice. 
• LDAP/HTTP/Session authentication

Fixes for these bugs can now be downloaded from the Sourceforge download engine... 

Bugs yet to be fixed

• Users having migrated from 0.0.4.x gets an "error" when editing Asset templates. This is due to a missing field (UUID) in the SQL asset tables. A fix will be provided in the RC2 release (should not be long in coming) in the form of a mysql database update.
• Login error can occure if you are currently logged in and try to access the default brage CM directory using index.php. Temporary fix is to make sure you log off usign the "Logoff ..." menu option, or access http://servername/brage/logout.php before logging in again.
• Adding/editing of users does not set the password field in the DB. A fix has been uploaded to the SF bug system. Download it from BUG 2219260 Replace the downloade file with the admin_user.php file in your Brage directory.

Hopefully there won't be that many more to come but you never know :-)

General info for users migrating from 0.0.4.

With the 0.1.0-RC1 release, adding profiles as well as assets are no longer needed. One now defines which assets should be used in CM Events when creating/editing the asset.

After a successful migration, go to the Admin -> Manage -> Asset Template.

Edit each of the templates you use and make sure you at least select the Enable for CM Events to be visible. All profiles migrated will already have this flag set, but when editing new or old ones it is handy to have this visible. You can also select the Show CM Settings. which holds the same setting.  as Enable for CM Events, but on a separate tab. If you use approval, make sure you also select Show CM Approvers.

It might also be the right time to change the order of the fields as they are displayed on the various templates. This is done by Editing a specific asset template and then clicking on the Field Sort Order tab. Move the various fiels around and save once you are happy with the new layout.

Currently only as a release candidate #1, but hopefully stable enough for use. 

Please goto the Project download page to download the 0.1.0 release.

Report any bugs/problems via mailinglist, forum or directly to email address found in the documentation.

Some of the changes in this relase are:

Major changes since 0.0.4-x
  * ALL $api_ settings in config.php have changed to $conf[<>]!!!
  * Changed WYSISYG editor from HTMLArea to FCKEditor
  * Profiles are migrated to assets making management easier!!
  * Improved security. (XSS, SQL injection etc)
  * Added pagination on the CM Event/Asset screens
  * User/Group administration is far easier.
  * Approval section and notification emails on CM Events have been improved.
  * Field-ordering of asset registration fields are customisable.
  * Added Ticket Reference. ($conf['cm_tag']) 
  * Asses does not need to be a member of groups.

            
TODO:
  * Update documentation  

   
Limitations:
  * Only database schema login currently works.
  * When an CM Event is saved in Complete/Locked status, no warning is given
    that it cannot be edited again once the user leaves the edit screen. 
 

Anyway, if you have downloaded Brage CM 0.0.4-2, make sure you also download this patch to bring your install up to v0.0.4-4. 

This patch fixes the following issues:

Fixes from 0.0.4-3

• CM Event - When adding/editing an entry and the Event Date field is filled out, the update time would always stay the same as the Event date.
• Calendar popup did not add a space between year and hour.

• Some browsers did not like that field names started with a number.
• strtotime() function have changed and does not like the "-" separator between date and time.
• IP verification failed on entries with 0's.

See the readme file for installation instructions.

This project will in no way compete with commercially available change management solutions, but it will provide an easy and efficient way to make sure you have a complete record of whatever you want to keep track on in terms of changes...

A simple asset management module is now also part of Brage - CM (which is becoming more and more functional- and less and less simple!)

Current Status:

• Release 0.1.0-RC1 is available for download from Sourceforge Project download page.

Features:

• PHP Based application
• Profile based entries (a profile can be anything you want to keep CM logs on)
• Group based security (profiles can be grouped together). Users are assigned to groups.
• Future cross platform independent database support (using ADODB library)
• Multiple authentication schemes supported (database, LDAP, HTTP Auth)
• WYSIWYG editor (Internet Explorer, Mozilla, Firefox, Opera, Safari using FCKEditor)
• Group based security
• Works on Linux/Unix and Windows (Apache and IIS)

Next Release: * A final release for v0.0.4 is out. Check out the News section for more info.

Mailing Lists * brage-cm-users

What would you like to see in this application? Do you have ideas that would improve Brage, please drop me an email on thomas.nilsen (at) doc-s.co.uk.

 
Roadmap

• Move profiles into the assets module. No longer need for separate assets/profiles (Completed!)
• Provide import script of data collected from Windows hosts via VB script (Near completion - need some testing)

v0.x.y

• Become an ITIL type application with features normaly found in an ITIL/CMDB type application.
• Allow building of a hieracy of assets that shows how differnet assets depend on each other (something that Configuration Management is all about)
• Improved approval functions on CM Events.
• Email subscription to changes
• Templates to allow a predefined documentation to be loaded on creation of new CM events.
• Improved Search Function
• Reporting function
• Improve GUI / CSS
• Complete DELETE function to make sure no "ghost" data exists.
• Export to CSV/TXT/XML format for the various listings (assets, profiles, events)
• Creating SQL structures for PostgreSQL, Oracle, MSSql.
• Asset templates to allow the creation of custom defined asset types
• Documentation
• Improved error logging/detection
• Event error logging to SQL base?
• Windows 32 binary to allow automatic registering/update of assets (run from login script or similar)
• Internationalisation

Why the name?

Brage was one of the gods in Norse Mythology. Being the good of eloquence and poetry, his speech was always the fairest.... As Change Management is about being fair in documenting any change, I thought it would fit well.. (better than Tor or Loke I suppose...)