as discussed in a meeting this morning with @catmorales and @jusabatier , we feel that it'd be better to enforce that rule for each release/release candidate. Sure, It calls for some testing, but there shouldn't be regressions from bugfixes, and this way we're more aligned with the stable branches of MapStore.
as discussed in a meeting this morning with @catmorales and @jusabatier , we feel that it'd be better to enforce that rule for each release/release candidate. Sure, It calls for some testing, but there shouldn't be regressions from bugfixes, and this way we're more aligned with the stable branches of MapStore.
that topic was discussed in https://github.com/georchestra/mapstore2-georchestra/issues/573#issuecomment-1348680341 too but the stable update to MS 2022.02.02 (geosolutions-it/MapStore2@814ac152) was forgotten/missed when publishing the final https://github.com/georchestra/mapstore2-georchestra/releases/tag/2022.02.00-geOrchestra release which ships with geosolutions-it/MapStore2@15c079322f4ce44f73f957bd145a1bf209c695f2
Thus, we lack some bugfixes from https://github.com/geosolutions-it/MapStore2/blob/2022.02.xx/CHANGELOG.md#20220201-2022-11-16 and all the commits that happened for https://github.com/geosolutions-it/MapStore2/blob/2022.02.xx/CHANGELOG.md#20220202-2022-12-13 ...