Release 2.26.0 #7895

petersmythe · 2024-09-16T15:59:05Z

Pulling together the following:

Of interest - ignore the following failure:

Workflow "Azure BlobStore Integration / Azure online" consistently fails GeoWebCache/geowebcache#1321
A new workflow added to geowebcache is consistently failing - not a blocker. Test is just out of budget to test s3 integration.

Checklist

I have read the contribution guidelines.
I have sent a Contribution Licence Agreement (not required for small changes, e.g., fixing typos in documentation).
First PR targets the main branch (backports managed later; ignore for branch specific issues).
All the build checks are green (see automated QA checks).

For core and extension modules:

New unit tests have been added covering the changes.
Documentation has been updated (if change is visible to end users).
The REST API docs have been updated (when changing configuration objects or the REST controllers).
There is an issue in the GeoServer Jira (except for changes that do not affect administrators or end users in any way).
Commit message(s) must be in the form [GEOS-XYZWV] Title of the Jira ticket.
Bug fixes and small new features are presented as a single commit.
Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

…2.27-SNAPSHOT, 33-SNAPSHOT, 1.27-SNAPSHOT

…maintain versions of docs

petersmythe · 2024-09-16T16:23:59Z

doc/en/developer/source/release/guide/index.rst

@@ -102,7 +102,7 @@ When creating the first release candidate of a series, there are some extra step

    ant -f build/rename.xml 

-  .. note:: use of sed
+  .. note:: Alternative use of sed


Should this whole note not simply be removed, or do some people still prefer sed over build/rename.xml?

If the rename.xml scrip is working for you; then yes we could remove the manual sed instructions now.

petersmythe · 2024-09-16T17:11:21Z

doc/en/developer/source/release/guide/index.rst

-  * create new jobs, copying from the existing stable jobs, and edit the branch.
-  * modify the last line of the live-docs builds, changing ``stable`` to ``maintain`` for the previous stable branch. The new job you created should publish to ``stable``, and the main development branch will continue to publish to ``latest``.
+  * create new jobs, duplicating from the three existing stable jobs (geoserver-2.11.x, geoserver-2.11.x-docs and geoserver-2.11.x-nightly), and edit the branch specifier to the new branch (e.g. `2.11.x` -> `2.12.x`).
+  * delete the trigger on the previous `geoserver-2.11.x-nightly` job to not trigger the `geoserver-release-docker` job


I think this needs to be added @jodygarnett ?

I think personally I open up all the jobs as distinct tabs, "disable them", and then update the code, and then enable first geotools, then geowebcache, then geoserver (to avoid overloading build server).

The alternative is killing lots of jobs so the one you are working on has a chance to run.

petersmythe · 2024-09-16T17:11:53Z

doc/en/developer/source/release/guide/index.rst


-* Update the cite tests on build.geoserver.org:
+* ~~Update the cite tests on build.geoserver.org~~:


Leave this here in the hopes that we will one day return to cite tests?

maybe marked as "not currently used", but I have stopped trying to promote cite tests as a sponsorship target.

petersmythe · 2024-09-16T17:17:47Z

doc/en/developer/source/release/guide/index.rst

@@ -155,8 +155,6 @@ When creating the first release candidate of a series, there are some extra step
 * Switch to the new branch and update the documentation links, replacing ``docs.geoserver.org/latest`` with ``docs.geoserver.org/2.12.x`` (for example):

  * ``README.md``
-  * ``doc/en/developer/source/conf.py``


I think the ant build/rename.xml has already updated these 2 conf.py files, hasn't it @jodygarnett ?

Does the README.md still need to be changed - probably yes.

I hope the rename.xml does what is needed. But I still wish to document the manual process (if needed).

petersmythe · 2024-09-16T17:38:30Z

Depends on geotools/geotools#4904 and GWC new snapshots being available

jodygarnett · 2024-09-25T01:38:12Z

@petersmythe I have my own notes from the release process to share. Can we untangle the developers guide improvements from the creation of 2.27-SNAPSHOT?

No longer any need to enable branch protection
Use include to pull the example lines from build.xml

Update index.html

    <dl>
      <dt>GeoServer 2.21.x
          ( <a href="https://docs.geoserver.org/2.21.x/en/user/">User Manual</a>
          | <a href="https://docs.geoserver.org/2.21.x/en/developer/">Developer Manual</a>
          | <a href="https://docs.geoserver.org/2.21.x/en/docguide/">Documentation Guide<a/>
          )
      </dt>
    </dl>

Create next major release in Jira (removing references to RC)
Disable the maintenance jobs? Leave the maintenance jobs around for a bit, they only run if someone back ports a change. Update the doc snippet at the end...
Disable all the jobs so you can test in isolation (open them all in multiple tabs to ease frustration)
Maintenance -> archive
- 2.24.x - no change needed
- 2.24.x-docs -  # Change this when releasing # LINK=maintain # LINK_PATH=/var/www/geoserverdocs/$LINK ... # echo "link $VER to $LINK_PATH" # ssh -oStrictHostKeyChecking=no -p 2223 $REMOTE "if [ -e $LINK_PATH ]; then rm $LINK_PATH; fi && ln -s $REMOTE_PATH $LINK_PATH" # # echo "docs published to https://docs.geoserver.org/$LINK/en/user"
- 2.24.x-nightly - uses scp to copy to 2.24.x folder (so there must be a symbolic link on docs.geoserver?)

Stable to maintain
- 2.25.x - no change needed
- 2.25.x-docs LINK=maintain
- 2.25.x-nightly - no change needed
Dev to stable
- 2.26.x - copied from 2.25.x (changing to 2.25.x) update 2.25.x --> 2.26.x
- 2.26.x-docs - copied from 2.25.x-docs (changing to 2.25.x)  LINK=stable
- 2.26.x-nightly - copied from 2.25.x-nightly (changing to 2.25.x)
Dev
- Can now run to test out the new dependencies

Docker - need to update the Dockerfile
Remove reference to the cite tests

stale · 2024-12-28T11:25:34Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale · 2025-01-11T11:50:23Z

This issue has been automatically closed because it has not had recent activity. Please re-submit with updates if you want to resume work on this topic. Thank you for your contributions.

Peter Smythe added 3 commits September 16, 2024 17:54

Use build/rename.xml to update version in all pom.xml files to next: …

6b6fb30

…2.27-SNAPSHOT, 33-SNAPSHOT, 1.27-SNAPSHOT

Instruction no longer necessary as we now link to latest, stable and …

513a605

…maintain versions of docs

Clarify this is an alternative: using sed

67e086b

petersmythe commented Sep 16, 2024

View reviewed changes

Peter Smythe added 2 commits September 16, 2024 18:27

Update docs: No longer need to enable GitHub branch protection

5965af5

Update docs: Clarify instructions

a18351a

petersmythe commented Sep 16, 2024

View reviewed changes

Update docs: Question whether this should be here or not

a03e027

petersmythe commented Sep 16, 2024

View reviewed changes

stale bot added the stale label Dec 28, 2024

stale bot closed this Jan 11, 2025

petersmythe deleted the peter-release-v2.26.0 branch February 19, 2025 10:00

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Release 2.26.0 #7895

Release 2.26.0 #7895

petersmythe commented Sep 16, 2024 •

edited by jodygarnett

Loading

petersmythe Sep 16, 2024

jodygarnett Sep 17, 2024

petersmythe Sep 16, 2024

jodygarnett Sep 17, 2024

petersmythe Sep 16, 2024

jodygarnett Sep 17, 2024

petersmythe Sep 16, 2024

jodygarnett Sep 17, 2024

petersmythe commented Sep 16, 2024 •

edited

Loading

jodygarnett commented Sep 25, 2024

stale bot commented Dec 28, 2024

stale bot commented Jan 11, 2025


		* Update the cite tests on build.geoserver.org:
		* ~~Update the cite tests on build.geoserver.org~~:

Release 2.26.0 #7895

Release 2.26.0 #7895

Conversation

petersmythe commented Sep 16, 2024 • edited by jodygarnett Loading

Checklist

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

petersmythe commented Sep 16, 2024 • edited Loading

jodygarnett commented Sep 25, 2024

stale bot commented Dec 28, 2024

stale bot commented Jan 11, 2025

petersmythe commented Sep 16, 2024 •

edited by jodygarnett

Loading

petersmythe commented Sep 16, 2024 •

edited

Loading