Release 1.2.0

[ivanperez-keera]

Description

Version 1.2.0 of Ogma is ready and should be closed.

Type

• Management: release and publication.

Additional context

None.

Requester

• Ivan Perez.

Method to check presence of bug

Not applicable (not a bug).

Expected result

• Cabal files indicate new version number, constraints are adjusted as needed, commit is tagged with version number.

Desired result

• Cabal files indicate new version number, constraints are adjusted as needed, commit is tagged with version number.

Proposed solution

• Cabal files indicate new version number, constraints are adjusted as needed, commit is tagged with version number.

Further notes

• Should be uploaded to hackage.

[ivanperez-keera]

Change Manager: Confirmed that a new version is ready to be released.

[ivanperez-keera]

Technical Lead: Confirmed that the issue should be addressed.

[ivanperez-keera]

Technical Lead: Issue scheduled for Ogma 1.2.0, to be released TODAY.

Fix assigned to: @ivanperez-keera.

[ivanperez-keera]

Implementor: Solution implemented, review requested.

[ivanperez-keera]

Change Manager: Verified that:

• Solution is implemented:
  • The code proposed compiles and passes all tests. Details:
    Docker image:

    FROM ubuntu:trusty
    
    RUN apt-get update
    
    RUN apt-get install --yes software-properties-common
    RUN add-apt-repository ppa:hvr/ghc
    RUN apt-get update
    
    RUN apt-get install --yes ghc-8.6.5 cabal-install-2.4
    RUN apt-get install --yes libz-dev
    
    ENV PATH=/opt/ghc/8.6.5/bin:/opt/cabal/2.4/bin:$PWD/.cabal-sandbox/bin:$PATH
    
    RUN cabal update
    RUN cabal v1-sandbox init
    RUN cabal v1-install alex happy
    RUN apt-get install --yes git
    
    # We install the application first and then test it, in case any tests need to
    # run the tool.
    CMD git clone $REPO && \
        cd $NAME && \
        git checkout $COMMIT && \
        cd .. && \
        cabal v1-install $NAME/$PAT**/ --enable-tests && \
        cabal v1-install $NAME/$PAT**/ --enable-tests --run-tests -j1

    Command:

    $ docker run -e "REPO=https://github.com/ivanperez-keera/ogma" -e "NAME=ogma" -e PAT="ogma-" -e "COMMIT=e9dcc89408e79e9a2f5d8d558e41660a67bccabf" -it ogma-test

  • The solution proposed fixes the issues described.
    The following docker image installs ogma enforcing the new version via compiler constraints.

    FROM ubuntu:trusty
    
    ENV DEBIAN_FRONTEND=noninteractive
    
    RUN apt-get update
    
    RUN apt-get install --yes software-properties-common
    RUN add-apt-repository ppa:hvr/ghc
    RUN apt-get update
    
    RUN apt-get install --yes ghc-8.6.5 cabal-install-2.4
    RUN apt-get install --yes libz-dev
    
    ENV PATH=/opt/ghc/8.6.5/bin:/opt/cabal/2.4/bin:$PWD/.cabal-sandbox/bin:$PATH
    
    RUN cabal update
    RUN cabal v1-sandbox init
    RUN cabal v1-install alex happy
    RUN apt-get install --yes git
    
    # We install the application first and then test it, in case any tests need to
    # run the tool.
    CMD git clone $REPO && \
        cd $NAME && \
        git checkout $COMMIT && \
        cd .. && \
        cabal v1-install $NAME/$PAT**/ --enable-tests \
          --constraint="ogma-cli==1.2.0" \
          --constraint="ogma-core==1.2.0" \
          --constraint="ogma-language-fret-reqs==1.2.0" \
          --constraint="ogma-language-smv==1.2.0" \
          --constraint="ogma-language-copilot==1.2.0" \
          --constraint="ogma-language-cocospec==1.2.0" \
          --constraint="ogma-language-c==1.2.0" \
          --constraint="ogma-language-jsonspec==1.2.0" \
          --constraint="ogma-extra==1.2.0" \
          --constraint="ogma-spec==1.2.0" \
          && \
        cabal v1-install $NAME/$PAT**/ --enable-tests --run-tests -j1

    Command:

    $ docker run -e "REPO=https://github.com/ivanperez-keera/ogma" -e "NAME=ogma" -e PAT="ogma-" -e "COMMIT=e9dcc89408e79e9a2f5d8d558e41660a67bccabf" -it ogma-verify-117

• Implementation is documented. Details:
  No need for updates to documentation.
• Change history is clear.
• Commit messages are clear.
• Changelogs are updated.
• Examples are updated. Details:
  No examples affected.
• Required version bumps are evaluated. Details:
  No bump needed; bump executed.

[ivanperez-keera]

Change Manager: Implementation ready to be merged.