Upgrade Considerations - Updated

Tue, 07 Nov 2006 14:29:00 GMT

It is getting close to the first release of version 0.7.X of the issue tracker (I promise). The goal is by the end of October to have the first beta release. For those adventurous types, the upgrade scripts are already in the SVN repository but there are still issues to work out before the end of the month. Please refer to the issue tracker for outstanding issues.

In order to prepare your installation for upgrading there are a few things that administrators should know.

Since the user system has changed (once again) over to the .NET 2.0 Membership Provider users will have to have a unique email address. If duplicate email addresses exist the upgrade will not function properly.

The upgrade scripts will set users to unauthorized if the active flag is turned off in the current version, this means you should set users that are no longer in use to inactive so that they will not be able to log in once the upgrade is complete.

Because passwords are now hashed, the upgrade will create random passwords for each user. This means you will not be able to login with existing passwords and users will have to use the forgot password functionality of to generate another password that will be emailed directly to them.

*** This has changed since the initial design. The password format has been changed to encrypt the passwords. This opens up functionality for password recovery and resets. The installer will encrypt any password that meets the password requirements (7 characters by default) and will randomly generate a new password for any user whose password does not meet these requirements. In the works is emailing the user his / her new password. The user can also use the password recovery page (in the works).

Currently there are no plans to upgrade the Environment, Hardware and Operating System fields. If this causes a lot of concern then the final version may contain upgrade logic to migrate these fields to new custom fields.

All in all progress is being made and we are very close to wrapping up a first release. I look forward to moving forward after this release with a more timely release schedule as well.

Development

Upgrade Considerations - Updated