Project

General

Profile

Bug #4337

1.0 -> 2.0 upgrade issues tracking bug

Added by Chad Berkley about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Chad Berkley
Category:
general
Target version:
2.0.0
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

Blocks Kepler - Bug #3898: update .kepler instead of removing it between versionsResolved03/17/2009

Blocks Kepler - Bug #4514: Files are being saved in the Kepler installation directoryResolved10/29/2009

Blocks Kepler - Bug #4666: identify problems with converting .kepler-1.0 to .kepler-2.0Resolved01/13/2010

Blocks Kepler - Bug #4722: find 1.0 -> 2.0 .kepler incompatibilitiesResolved02/02/2010

History

#1 Updated by David Welker over 9 years ago

Are there any remaining tasks for this bug?

#2 Updated by Chad Berkley over 9 years ago

All tasks are closed. Closing this tracking bug.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4337

Also available in: Atom PDF