Skip to content

Commit

Permalink
Merge pull request #14 from jburel/organise
Browse files Browse the repository at this point in the history
organise the releases under one section
  • Loading branch information
jburel authored Aug 19, 2024
2 parents 83abc79 + e00990b commit 54e62e7
Show file tree
Hide file tree
Showing 6 changed files with 59 additions and 13 deletions.
17 changes: 17 additions & 0 deletions docs/components-release.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
Components release
==================

The following sections summarize the release process of the various components of the software stack.
Note this is not an exhaustive list of all tools release process.


.. toctree::
:maxdepth: 1

cpp-development
gradle-development
java-development
python-components
omero-release-process
omero-web-release-process

26 changes: 26 additions & 0 deletions docs/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@

import sys
import os
import shutil

linkcheck_ignore = []
extensions = ['sphinx.ext.extlinks']
Expand Down Expand Up @@ -245,3 +246,28 @@
r'https://oss.sonatype.org/.*', # Requires login
github_root + 'ome/'
]

def copy_legacy_redirects(app, exception):
"""
see: https://tech.signavio.com/2017/managing-sphinx-redirects
"""
print("Adding redirects:")
redirect_files = [
'python-development.html',

]
if app.builder.name == 'html':
for html_src_path in redirect_files:
target_path = app.outdir + '/' + html_src_path
src_path = app.srcdir + '/' + html_src_path
if os.path.isfile(src_path):
target_dir = os.path.dirname(target_path)
if not os.path.exists(target_dir):
os.makedirs(target_dir)
shutil.copyfile(src_path, target_path)
print(" %s" % html_src_path)


def setup(app):
app.connect('build-finished', copy_legacy_redirects)

4 changes: 2 additions & 2 deletions docs/cpp-development.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
C++ components
==============
C++ components (deprecated)
===========================

This document describes the conventions and process used by the OME team for
developing, maintaining and releasing its C++ components.
Expand Down
7 changes: 1 addition & 6 deletions docs/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -17,19 +17,14 @@ be valuable to a wider audience.
team-communication
team-workflow
ansible-development
java-development
gradle-development
cpp-development
development-tools
deployment-tools
continuous-integration
editing-docs
jekyll
data-model-schema
schema-changes
python-development
omero-release-process
omero-web-release-process
components-release

Information specific to developing OMERO, the OME Data Model and file formats,
and Bio-Formats can be found in their respective developer documentation
Expand Down
10 changes: 5 additions & 5 deletions docs/python-development.rst → docs/python-components.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Python development
==================
Publish to PyPI
===============

Release process
---------------
Expand Down Expand Up @@ -52,9 +52,9 @@ To complete the release, push the master branch and the release tag to origin::

$ git push origin master v5.8.0

Publishing to Pypi
==================
Publishing
----------

Many of the OME Python repositories use GitHub actions to publish to `Pypi <https://pypi.org/>`_
Many of the OME Python repositories use GitHub actions to publish to PyPI_
when a new tag is created and pushed to GitHub.
This is typically specified in a file such as `.github/workflows/publish_pypi.yml`.
8 changes: 8 additions & 0 deletions docs/python-development.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<html>
<head>
<meta http-equiv="refresh" content="1; url=../" />
<script>
window.location.href = "python-components.html"
</script>
</head>
</html>

0 comments on commit 54e62e7

Please sign in to comment.