...
There would be significant benefit to running a cloud instance of the actively supported branches of DSpace (currently dspace-4_x, dspace-5_x, dspace-6_x). This would ensure that anyone in the community would have access to latest code under consideration for a release.
In particular, this would allow the DCAT team to conduct a testathon on a code base prior to the creation of a release/release candidate.
The DSpace 5.7 and DSpace 6.1 releases incorporated last-minute changes that unexpectedly introduced bugs into the system that were only discovered by running end to end functionality in DSpace. Because of these bugs, new releases will need to be created.. The availability of a widely-accessible stable test environment might have prevented these bugs.
In the past, for For major DSpace releases, a release candidate is generated. In order for the release candidate to be tested, host institutions need needed to install, deploy and test the release candidate on their own network. This process can provide a valuable verification of installation and migration instructions, but it also imposes a significant burden on each host institution that participates in the test. This burden lengthens the window of time required to conduct system testing.
What is required?
- ...
Related Conversations
- DCAT Meeting August 2017
- DSpace Developer Meeting 2017-08-09
- The log of this conversation was truncated. See notes below.
...