Bug #4337
1.0 -> 2.0 upgrade issues tracking bug
Start date:
08/26/2009
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
4337
Description
We need to come up with a set of issues to handle the upgrade between kepler 1.0 and kepler 2.0. The upgrade path should be smooth and should include updating the .kepler directory without the user having to delete their cached data/actors. Make any 2.0 upgrade bugs block this bug.
Related issues
History
#1 Updated by David Welker almost 11 years ago
Are there any remaining tasks for this bug?
#2 Updated by Chad Berkley almost 11 years ago
All tasks are closed. Closing this tracking bug.
#3 Updated by Redmine Admin almost 8 years ago
Original Bugzilla ID was 4337