Project

General

Profile

Actions
Copy link

Bug #4337

closed

1.0 -> 2.0 upgrade issues tracking bug

Added by Chad Berkley over 14 years ago. Updated about 14 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 versionsResolvedAaron Aaron03/17/2009

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

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

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

Actions
Actions
Copy link
 #1

Updated by David Welker about 14 years ago

Are there any remaining tasks for this bug?

Actions
Copy link
 #2

Updated by Chad Berkley about 14 years ago

All tasks are closed. Closing this tracking bug.

Actions
Copy link
 #3

Updated by Redmine Admin about 11 years ago

Original Bugzilla ID was 4337

Actions
Copy link

Also available in: Atom PDF