prepare v11.0.0 (#3023)

---------

Co-authored-by: Matthias Riße <[email protected]>

Author: ReimarBauer

CHANGES.rst

@@ -1,6 +1,18 @@
 Changelog
 =========
 
+Version 11.0.0
+~~~~~~~~~~~~~~
+
+This is primarily a refactoring release.
+
+Reimar Bauer has removed our dependency on the pyfilesystem2 (fs) library, replacing it with Pathlib and os.path.
+Matthias Riße and Reimar Bauer have improved the stability of our test setup.
+The generation of demo data has been unified, and various deprecations have been resolved.
+
+All changes:
+https://github.com/Open-MSS/MSS/milestone/107?closed=1
+
 Version 10.2.1
 ~~~~~~~~~~~~~~
 

docs/development.rst

@@ -7,14 +7,15 @@ This chapter will get you started with MSS development.
 
 MSS is written in Python.
 
-Once a stable release is published we do only bug fixes in stable and release regularly
-new minor versions. If a fix needs a API change or it is likely more a new feature you have
-to make a pull request to the develop branch. Documentation of changes is done by using our
-`issue tracker <https://github.com/Open-MSS/MSS/issues>`_.
+Development work is exclusively performed on the **develop** branch.
+Bug fixes are backported to the `stable` branch whenever feasible.
+If a bug fix cannot be backported, corresponding updates will be made to the develop branch.
+We release new minor versions on a regular basis.
+New features should be submitted as pull requests against the develop branch.
+Changes and documentation are managed through our `issue tracker <https://github.com/Open-MSS/MSS/issues>`__.
 
 When it is ready the developer version becomes the next stable.
 
-
 The stable version of MSS is tracked on `BLACK DUCK Open Hub <https://www.openhub.net/p/mss>`_
 
 
@@ -456,35 +457,43 @@ After filling the template completely click on Pull request
 
 
 
-Merging stable into develop
----------------------------
+Creating a new minor, patch level release
+-----------------------------------------
 
-Bug fixes we have done in stable we need to merge regularly into develop too::
+The stable branch will only receive critical bug fixes, and security patches. These patches must either address a bug that is only present on stable, be a backport of a patch that was already merged into develop, or there must simultaneously be a PR addressing the same issue on develop.
 
-   git checkout stable
-   git pull [email protected]:Open-MSS/MSS.git stable
-   git checkout develop
-   git pull [email protected]:Open-MSS/MSS.git develop
-   git checkout -b merge_stable_to_develop
-   git merge stable
-   git push [email protected]:Open-MSS/MSS.git merge_stable_to_develop
+We will review changes for both branches when there is no backport from develop possible.
 
+For a new minor/patch release
 
-Then create the proposed merge request. The merge request must *not* be squashed or rebased.
-To allow the merging, the requirement for a linear-history must be disabled *temporarily*
-for the develop branch and one needs to ensure that the merge request is accepted with a
-regular merge with merge commit. Remove the merge_stable_to_develop branch if still present.
+* make sure all issues for this milestone are closed or moved to the next milestone
+* update CHANGES.rst, based on git log
+* check version number of upcoming release in pyproject.toml
+* verify that pyproject.toml, MANIFEST.in are complete
+* Update the version in the lock file by `pixi lock`
+* tag the release::
 
+   git tag -s -m "tagged/signed release X.Y.Z" X.Y.Z
+   git push origin X.Y.Z
+
+* write a release information on https://github.com/Open-MSS/MSS/releases
+* create a release on anaconda conda-forge
+* announce on:
+
+  * Mailing list
+  * Mastodon (follow https://fosstodon.org/@MSS)
 
-Creating a new release
-----------------------
+
+
+Creating a new major release
+----------------------------
 
 * make sure all issues for this milestone are closed or moved to the next milestone
 * update CHANGES.rst, based on git log
 * check version number of upcoming release in pyproject.toml
 * verify that pyproject.toml, MANIFEST.in are complete
 * Update the version in the lock file by `pixi lock`
-* for a new stable release merge from develop to stable
+* for a new major release rename the existing stable branch to oldstable and recreate it from the develop branch
 * tag the release::
 
    git tag -s -m "tagged/signed release X.Y.Z" X.Y.Z
@@ -519,6 +528,12 @@ MSS takes part in `Google Summer of Code <https://summerofcode.withgoogle.com/>`
 as a `sub-organization of Python Software Foundation (PSF) <https://python-gsoc.org/>`_.
 
 
+GSoC'25 Projects
+................
+
+- `Annapurna Gupta: Mission support system : View Layout and Storing : GSOC2025 <https://github.com/Open-MSS/MSS/wiki/Annapurna-Gupta:-Mission-support-system-:-View-Layout-and-Storing-:-GSOC2025>`_
+
+
 GSoC'24 Projects
 ................
 

pixi.lock

@@ -1,6 +1,6 @@
 [project]
 name = "open-mss"
-version = "10.2.1"
+version = "11.0.0"
 description = "MSS - Mission Support System"
 readme = "README.md"
 classifiers = [