Kbase 15375: Roundtable support of multiple Progress versions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Roundtable support of multiple Progress versions
Subject:
========
Roundtable support for multiple progress versions
Scenarios:
==========
Concurrently support multiple versions:
---------------------------------------
Application partners may be supporting four or five legacy versions of
their application. These legacy versions may be in different Progress
versions. All new development occurs in the current version of
Progress. All bugs are fixed in the application version and Progress
version that they occur. The new development is in Progress version 7,
but once a month a patch release in Progress version 6 is made.
Possible solution:
------------------
The version 7 and 8 products are all managed by Roundtable in a single
repository. The repository contains all object versions, and objects can
be easily moved from one version to the next. The version 6
application is maintained in its own repository. These objects cannot
be migrated to the v7 or v8 application through Roundtable.
The end-user must have a Roundtable license for each platform
supported: V7 character, v7/v8 GUI, v6 character.
Implementing Roundtable to upgrade an existing product:
-------------------------------------------------------
An IS shop is updating their application to GUI Progress version 8.
They realize that a lot of changes are going to occur to update their
product, and they are very concerned about having accurate testing
information.
Possible Solution:
------------------
They implement Roundtable and load the application under Progress
version 7. By doing this they will be able to patch and deploy the
version 7 application while the version 8 application is under
development. Since they have the old version in Roundtable from v7,
they have a lot of information about the changes that they made during
the port to version 8. With that information they should be able to
better test the application, and deliver a better Progress application.
. The end-user must have a Roundtable application license for each
application: V7 character,V7/V8 GUI.
New Development of GUI and character product:
---------------------------------------------
A new development shop purchases Progress because of its portability.
They are interested in re-writing an old RPG package in Progress.
They know they need to write a GUI application, but they have a large
character customer base with character Unix machines. They want to
write an application that supports both environments from a single code
e base.Progress lets them do that, but Roundtable needs to run both
character and GUI to test and deploy the application.
Possible Solution:
---------------------
Install the Roundtable repository on the Unix machine and develop
portable applications on the Windows client. The primary
development would be done using the UIB in TTY mode. The testing
would be done in Character Roundtable. Roundtable would
automatically migrate the code created on the Windows
client to the Unix testing area. Changes can be made in the character
area using Roundtable version 7.3Cfor character.
The end-user must have a Roundtable license for each platform
supported: V7 character, V7/V8 GUI.
Issues related to multiple version support:
-------------------------------------------
Progress v8-v6 incompatibility:
Roundtable must deliver coordinated releases between the GUI
products. Both products must support the same database structure.
When a new version of Roundtable was available the customer would
have to update all their Roundtable licenses.
Overhead of performing quality assurance. Does version 6.2 work
with 7.3, or does 6.3 work with 7.2.
Progress Software Technical Support Note # 15375