-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2024.01.01 #10385
Comments
@offtherailz I've checked all preliminary checks on top of the list since they are already ok, I think. Please double check. |
@offtherailz @tdipisa I tried several times to create a new project but this error occurs
|
@offtherailz can you please have a look at the above? Thank you |
Hi @ElenaGallo It worked for me:
I tested the same with master and 2024.01.xx for version. both worked for me, on my linux machine. |
@MV88 can you please do a try? |
no issue on my side as well
|
@tdipisa Release done. Up to you to update release notes and send the email to the mailing list tomorrow. |
…s edits in dashboards Description: - fix the issue of misleading persistence of CSW advanced settings edits in dahsboards instead of showing the default csw with its default advanced settings
…boards (#10412) Description: - fix the issue of misleading persistence of CSW advanced settings edits in dahsboards instead of showing the default csw with its default advanced settings
…s edits in dashboards (geosolutions-it#10412) Description: - fix the issue of misleading persistence of CSW advanced settings edits in dahsboards instead of showing the default csw with its default advanced settings
Setup and preliminary checks
This steps have to be followed always when preparing a new release.
http_proxy
,mapfish-print
orgeostore
, and do it if necessary accordingly with release calendar.geostore
, check if here is present the version specified. Release procedure is specified in the Readme.md file of the project.http_proxy
, check if here is present the version specified. Release procedure is specified in the Readme.md file of the project.mapfish-print
check if here is present the version specified. Release procedure is specified in the Readme.md file of the project.Before the Release
pom.xml
dependencies are all in fixed stable versions ( no-SNAPSHOT
usage release). If not, You use the actionUpdate dependencies versions
to fix them, setting:YYYY.XX.xx
node ./createProject.js
and insert the entries (for the rest simply press enter:release_project_test
YYYY.XX.xx
)../test_release_<release_number>
)cd ../test_release_<release_number>
npm install
npm run start:app
, then check that an empty homepage loads correctlyPrepare Release
Prepare Release
workflow on github actions with the following parameters:branch
YYYY.XX.xx (the release branch)1.7.0
)vYYYY.XX.mm
. This commit will contain the changelog and the updated version of the java modules.Submodules Update
on MapStoreExtension:YYYY.XX.xx
MapStore Stable deploy
-
branch
:vYYYY.XX.mm
(the version tag name, e.g. v2024.01.01)-
version
:${branch}-stable
( version to pass to the build )-
TAG_NAME
:${branch}-stable
(tag to assign to the docker hub image)-
branch
:vYYYY.XX.mm
(the version tag name, e.g. v2024.01.01)-
TAG_NAME
:${branch}-stable
(tag of the docker hub image, previously build)gs-stable
are visible without errors (typically authentication errors that was caused by the wrong auth-key).Create and Publish MapStoreExtension release
SampleExtension.zip
from the/dist
folder (or download the latest artifact).Create and Publish MapStore release
Create Release
workflow on github actions with the following parameters:branch
YYYY.XX.xx (the release branch)When the processes are finished, the release is ready to be published on github in draft mode.
Update ReadTheDocs
vYYYY.XX.mm
(click on "Versions" and activate the version of the tag, created when release was published)Default version
to point the release version in theAdvanced Settings
menu of the ReadTheDocs admin panelFinalize Release
Post Release
workflow on github with the following parameters:YYYY.XX.xx
(the release branch)-SNAPSHOT
E.g.1.7-SNAPSHOT
Other useful information
The text was updated successfully, but these errors were encountered: