Which pyaml version to use for test

[TeresiaOlsson]

Currently the tests are run using the latest version of pyaml in the git repository because of this:

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install "git+https://github.com/python-accelerator-middle-layer/pyaml.git"
          python -m pip install -e ".[test,epics,tango]"
          pip install flake8

This is causing problems because it blocks merges unless all changes are compatible with the changes in the main branch of pyaml. So for example it become difficult to add small bug patches, updates to the docs etc.

I suggest that we change the workflow to always test against the latest release on pypi and then add an optional workflow to be used by developers to test against the latest version on the main branch. It looks like we can always have both workflows triggered and allow to merge if it's only the developer test that fails.

What do you think?

[TeresiaOlsson]

@JeanLucPons and @gupichon Maybe you have suggestions for how to best handle it?

[TeresiaOlsson]

I'm wondering if maybe it would help to manage the dependencies in the future if we implement this workflow that we decided to use but never actually did? https://gist.github.com/digitaljhelms/4287848

This is where we decided it: https://github.com/orgs/python-accelerator-middle-layer/discussions/5

@gubaidulinvadim What do you think? I can add an item to our project list to set up that workflow on all the repositories.

[TeresiaOlsson]

I have implemented this workflow in PR #43 so we can test it.

[gubaidulinvadim]

I'm wondering if maybe it would help to manage the dependencies in the future if we implement this workflow that we decided to use but never actually did? https://gist.github.com/digitaljhelms/4287848

This is where we decided it: https://github.com/orgs/python-accelerator-middle-layer/discussions/5

@gubaidulinvadim What do you think? I can add an item to our project list to set up that workflow on all the repositories.

We indeed need a "stable" branch that is tested separately.

[TeresiaOlsson]

I have added the stable branch so we can try it out as part of the release workflow. But so far not done any changes to which versions that are used for the tests.

Probably it can wait to be changed until after the hackathon.