0009059: Have the ability to roll back a core update if the build process goes wrong

Description

If I go from 2.50 to 2.50MP1 and use the .obx files for the upgrade, I should be able to roll back to 2.50.

Currently, if something goes wrong as an example one is unable to update the database, there is no way to roll back the core update to the previous state before update.

Proposed Solution

Have the core be packaged prior to any upgrade. Then if some thing goes wrong you would have a .obx file which can be run to put the application and database back to previous state.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

feature request

0010938

acknowledged

iciordia

There is not a way to rollback an update when updating the core of the application

Notes
(0019420) rafaroda (developer) 2009-09-02 13:27	According to http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#How_to_Choose_the_Right_Severity [^] feature requests should not have Severity Critical. If there no reason why they are Critical please down their priority to Major: * New functionality that would significantly increase the user base of the product. * Usability improvements. Thanks.

(0035314) dalsasua (reporter) 2011-03-29 12:47	Reduced the severity, according to our reporting guidelines[1], because a FR cannot be critical: [1] http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#How_to_Choose_the_Right_Severity [^]

Issue History
Date Modified	Username	Field	Change
2009-05-16 13:04	kenzo	New Issue
2009-05-16 13:04	kenzo	Assigned To	=> rafaroda
2009-05-18 10:24	shuehner	Issue Monitored: shuehner
2009-05-22 16:11	rafaroda	Assigned To	rafaroda => pjuvara
2009-05-22 19:33	pjuvara	Assigned To	pjuvara => iciordia
2009-09-02 13:27	rafaroda	Note Added: 0019420
2009-10-16 12:03	psarobe	Relationship added	related to 0010938
2011-03-29 12:47	dalsasua	Note Added: 0035314
2011-03-29 12:52	dalsasua	Severity	critical => major