Skip to content
Snippets Groups Projects
Verified Commit dbf34784 authored by Daniel Hornung's avatar Daniel Hornung
Browse files

Release 0.2.1

parents 00e56468 abe59ccf
No related branches found
No related tags found
No related merge requests found
Pipeline #33752 passed
Pipeline: caosdb-octaveinttest

#33756

    ......@@ -28,5 +28,5 @@ COPY . /caosdb-octavelib
    WORKDIR /caosdb-octavelib
    RUN rm -rf .git
    RUN pip3 install -r doc/requirements.txt
    RUN pip3 install -r dev-requirements.txt
    RUN pip3 install -U -r doc/requirements.txt
    RUN pip3 install -U -r dev-requirements.txt
    ......@@ -47,6 +47,12 @@ build-testenv:
    image: docker:20.10
    script:
    - DOCKER_BASE_IMAGE="${CPPLIB_REGISTRY_IMAGE}"
    - if [[ "${CI_COMMIT_REF_NAME}" == release* ]] ; then
    echo "Release detected, choosing cpplib image from 'main' branch." ;
    DOCKER_BASE_IMAGE="$CI_REGISTRY/caosdb/src/caosdb-cpplib/testenv:main" ;
    else
    echo "CI_COMMIT_REF_NAME $CI_COMMIT_REF_NAME" ;
    fi
    - docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
    - if docker pull "$DOCKER_BASE_IMAGE" ; then
    echo "DOCKER_BASE_IMAGE=${DOCKER_BASE_IMAGE}" ;
    ......
    ## Summary
    *Please give a short summary of what the issue is.*
    ## Expected Behavior
    *What did you expect how the software should behave?*
    ## Actual Behavior
    *What did the software actually do?*
    ## Steps to Reproduce the Problem
    *Please describe, step by step, how others can reproduce the problem. Please try these steps for yourself on a clean system.*
    1.
    2.
    3.
    ## Specifications
    - Version: *Which version of this software?*
    - Platform: *Which operating system, which other relevant software versions?*
    ## Possible fixes
    *Do you have ideas how the issue can be resolved?*
    # Summary
    *Insert a meaningful description for this merge request here: What is the new/changed behavior?
    Which bug has been fixed? Are there related issues?*
    # Focus
    *Point the reviewer to the core of the code change. Where should they start reading? What should
    they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the
    specs, finding more corner cases, concrete questions)?*
    # Test Environment
    *How to set up a test environment for manual testing?*
    # Check List for the Author
    Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab
    comments for the reviewer. They should guide the reviewer through the changes, explain your changes
    and also point out open questions. For further good practices have a look at [our review
    guidelines](https://gitlab.com/caosdb/caosdb/-/blob/dev/REVIEW_GUIDELINES.md)
    - [ ] All automated tests pass
    - [ ] Reference related issues
    - [ ] Up-to-date CHANGELOG.md (or not necessary)
    - [ ] Appropriate user and developer documentation (or not necessary)
    - How do I use the software? Assume "stupid" users.
    - How do I develop or debug the software? Assume novice developers.
    - [ ] Annotations in code (Gitlab comments)
    - Intent of new code
    - Problems with old code
    - Why this implementation?
    # Check List for the Reviewer
    - [ ] I understand the intent of this MR
    - [ ] All automated tests pass
    - [ ] Up-to-date CHANGELOG.md (or not necessary)
    - [ ] Appropriate user and developer documentation (or not necessary)
    - [ ] The test environment setup works and the intended behavior is reproducible in the test
    environment
    - [ ] In-code documentation and comments are up-to-date.
    - [ ] Check: Are there specifications? Are they satisfied?
    For further good practices have a look at [our review guidelines](https://gitlab.com/caosdb/caosdb/-/blob/dev/REVIEW_GUIDELINES.md).
    /assign me
    /target_branch dev
    ......@@ -5,7 +5,13 @@ All notable changes to this project will be documented in this file.
    The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
    and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
    ## [0.2.0] ##
    ## [0.2.1] - 2023-02-17 ##
    ### Changed ###
    - Updated necessary Conan version to 1.54.
    ## [0.2.0] - 2022-09-26 ##
    ### Added ###
    ......
    # See https://octave.org/doc/interpreter/The-DESCRIPTION-File.html
    Name: caosdb
    Version: 0.2.0
    Date: 2022-09-22
    Version: 0.2.1
    Date: 2023-02-17
    Author: Daniel Hornung <d.hornung@indiscale.com>
    Maintainer: Daniel Hornung <d.hornung@indiscale.com>
    Title: Octave and Matlab library for CaosDB
    ......
    ......@@ -34,7 +34,7 @@ when creating the merge request. This allows our team to work with you on your r
    - If you have a suggestion for the [documentation](https://docs.indiscale.com/caosdb-octavelib/),
    the preferred way is also a merge request as describe above (the documentation resides in `src/doc`).
    However, you can also create an issue for it.
    - You can also contact us at **info (AT) caosdb.de** and join the
    - You can also contact us at **info (AT) caosdb.org** and join the
    CaosDB community on
    [#caosdb:matrix.org](https://matrix.to/#/!unwwlTfOznjEnMMXxf:matrix.org).
    ......
    ......@@ -34,6 +34,23 @@ guidelines of the CaosDB Project
    1. On [Releases](https://gitlab.indiscale.com/caosdb/src/caosdb-octavelib/-/releases), click "New release"
    2. Choose tag, type release title (same as tag), no milestone, possibly short release note, no
    manual assets are necessary, possibly link to documentation.
    1. Release title: `v0.2.0` (replace by actual release)
    2. Milestones: None
    3. Release date: today
    4. Release notes (replace release in link, copy from changelog file):
    ```
    # Changelog #
    See [full changelog](https://gitlab.indiscale.com/caosdb/src/caosdb-octavelib/-/blob/v0.2.0/CHANGELOG.md).
    ### Changed ###
    (Copy & paste from CHANGELOG.md)
    ```
    5. Assets:
    - URL: https://docs.indiscale.com/caosdb-octavelib/
    - Link title: Documentation
    - Type: Other
    8. Delete the release branch.
    ......
    ......@@ -4,7 +4,7 @@ certifi==2021.10.8
    chardet==4.0.0
    charset-normalizer==2.0.7
    colorama==0.4.4
    conan==1.52.0
    conan==1.54.0
    deprecation==2.1.0
    distro==1.6.0
    fasteners==0.16.3
    ......
    % Copyright (C) 2021 IndiScale GmbH <info@indiscale.com>
    % Copyright (C) 2021 Daniel Hornung <d.hornung@indiscale.com>
    % Copyright (C) 2021-2023 IndiScale GmbH <info@indiscale.com>
    % Copyright (C) 2021-2023 Daniel Hornung <d.hornung@indiscale.com>
    %
    % This file is a part of the CaosDB Project.
    %
    ......@@ -23,7 +23,7 @@ header = @(a_1, a_2, a_3) ...
    '<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">\n', ...
    ' <head>\n', ...
    ' <meta http-equiv="content-type" content="text/html; charset=utf-8" />\n', ...
    ' <meta name="date" content="2022-09-22"/>\n', ...
    ' <meta name="date" content="2023-02-17"/>\n', ...
    ' <meta name="generator" content="generate_html 0.4.0" />\n', ...
    ' <meta name="author" content="The Octave-Forge Community" />\n', ...
    ' <meta name="description" content="Octave-Forge is a collection of packages ', ...
    ......
    ......@@ -23,14 +23,14 @@ import sphinx_rtd_theme # type: ignore # noqa: 401
    # -- Project information -----------------------------------------------------
    project = 'OctaveCaosDB'
    copyright = '2022, IndiScale GmbH'
    copyright = '2021-2023, IndiScale GmbH'
    author = 'Daniel Hornung'
    # The short X.Y version
    version = '0.2'
    # The full version, including alpha/beta/rc tags
    # Example: release = '0.5.2-rc2'
    release = '0.2.0'
    release = '0.2.1'
    # -- General configuration ---------------------------------------------------
    ......
    0% Loading or .
    You are about to add 0 people to the discussion. Proceed with caution.
    Please register or to comment