Hi David, DSpace 7 is a temporary departure from those rules. We broke those rules only for DSpace 7 because otherwise DSpace 7 would never be "backwards compatible" with DSpace 6 and prior. We made this decision prior to the release of 7.0, as we realized that if we require 7.0 to have all the features of DSpace 6, it'd not be out for a very long time. So, DSpace 7.x is about bringing DSpace 6 forward into a completely new UI, and that means layering in more features in each 7.x release until this "backwards compatibility" is achieved.
You can see the reasons for the decision and all additional features still coming to DSpace 7.x here: https://wiki.lyrasis.org/display/DSPACE/DSpace+Release+7.0+Status I fully expect that with DSpace 8 we will revert back to the existing policies (which you referenced). The timeline for DSpace 8 is still TBD, but early notes are here: https://wiki.lyrasis.org/display/DSPACE/DSpace+Release+7.0+Status#DSpaceRelease7.0Status-Whenwill8.0planningbegin?IsthereaRoadmapfor8.0? Tim ________________________________ From: [email protected] <[email protected]> on behalf of David P. Steelman <[email protected]> Sent: Tuesday, October 18, 2022 1:12 PM To: DSpace Developers <[email protected]> Subject: [dspace-devel] DSpace 7 Version numbrring Hi All, Hoping to get some insight into DSpace version numbering. The https://wiki.lyrasis.org/dspace/releases page indicates that DSpace versions consist of [major].[minor] version numbers, and that "Major Releases: ... may include any or all of the following: new features, system improvements, architectural changes, bug fixes. Minor (Bug-Fix) Releases: ... will only include bug fixes to an existing major release" Looking through the DSpace 7 release notes (https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes) it is evident that each minor version includes new features, improvements, as well as bug fixes. There have also been occasional bug fix only "patch" releases (i.e., v7.1.1, v7.2.1). The most recent DSpace 7.4 release also included a backward-incompatible architectural change to the Angular front-end (for those customizing the front-end), specifically the removal of the "DataService" class (app/core/data/data.service.ts) and its replacement by the "BaseDataService" and "IdentifiableDataService" classes in PR #1791 (https://github.com/DSpace/dspace-angular/pull/1791). So just wondering what expectations, if any, we should have in regards to DSpace version numbers, especially in relation to backward-incompatible architectural changes. Thanks, David -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-devel/c2cf0828-0852-43f6-8821-f4299887a8den%40googlegroups.com<https://groups.google.com/d/msgid/dspace-devel/c2cf0828-0852-43f6-8821-f4299887a8den%40googlegroups.com?utm_medium=email&utm_source=footer>. -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-devel/CO3PR22MB3279EACEF59F755FB62F4459ED289%40CO3PR22MB3279.namprd22.prod.outlook.com.
