Difference between revisions of "SUNScholar/Software Release Cadence"
| Line 8: | Line 8: | ||
We run one of the larger repositories with 55,000 records and about 10,000 full text items. We also have a large admin and normal user base after two years operation. So although the demo DSpace website may work, things change radically in production environments, when doing version upgrades, not fresh installs, and having many records and users. | We run one of the larger repositories with 55,000 records and about 10,000 full text items. We also have a large admin and normal user base after two years operation. So although the demo DSpace website may work, things change radically in production environments, when doing version upgrades, not fresh installs, and having many records and users. | ||
===The Solution=== | ===The Solution=== | ||
| + | The Debian Linux distribution has a solution for always maintaining a stable version of software. They have an unstable, testing and stable repository of software. | ||
| + | All new items land in unstable. When the new items are then tested and if proved working, then they are moved to the testing repository. The items stay in the testing repository until all bugs have been revealed and removed.Then items in testing move to the stable repository. | ||
| + | |||
| + | This could suit DSpace very well. Those institutions that do not employ a full technology support stack, could then safely run the stable version of DSpace. Those institutions that have a full technology support stack could then run testing and help to get new software into unstable. | ||
| + | |||
| + | This would also help libraries in developing nations that do not normally have a full technology stack of expertise at their disposal to run the latest "stable" version of DSpace. | ||
Revision as of 12:11, 13 July 2014
Back to Guidelines
Introduction
This wiki page is related to a posting on the DSpace general mailing list, see link below.
http://sourceforge.net/p/dspace/mailman/message/31894819/
The Problem
We run one of the larger repositories with 55,000 records and about 10,000 full text items. We also have a large admin and normal user base after two years operation. So although the demo DSpace website may work, things change radically in production environments, when doing version upgrades, not fresh installs, and having many records and users.
The Solution
The Debian Linux distribution has a solution for always maintaining a stable version of software. They have an unstable, testing and stable repository of software. All new items land in unstable. When the new items are then tested and if proved working, then they are moved to the testing repository. The items stay in the testing repository until all bugs have been revealed and removed.Then items in testing move to the stable repository.
This could suit DSpace very well. Those institutions that do not employ a full technology support stack, could then safely run the stable version of DSpace. Those institutions that have a full technology support stack could then run testing and help to get new software into unstable.
This would also help libraries in developing nations that do not normally have a full technology stack of expertise at their disposal to run the latest "stable" version of DSpace.
