openlp-core team mailing list archive

[Stevan Pettit <1100424@xxxxxxxxxxxxxxxxxx>]

If you want to keep "testing" separate from "released", simply change
the application name in ..\trunk\openlp\core\__init__.py then add a
little code down-line to point OpenLP to a "custom data directory"
(similar to running portable).

Changing the application name will change the registry entry in Windows
and should change the config file in other O/S's.

When releasing a new version, change the name back to OpenLP.

Also, will "testing/development" be done in the 2.0 branch, or will it
be done in Trunk or both?

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/1100424

Title:
  allow running openlp 2.1 without affecting 2.0 data

Status in OpenLP - Worship Presentation Software:
  New

Bug description:
  I think it could be helpful for development and testing to allow
  running openlp 2.1 without affecting settings and data of the stable
  release 2.0.

  This way we could easily test and develop 2.0 bug fix releases and
  development 2.1 releases on the same machine.

  Later Openlp 2.1 could integrate a data/settings migration wizard for
  updating 2.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/1100424/+subscriptions