Releases and tags using semantic versioning

[miralgj]

It would be beneficial if the project made "dot" releases or tags as bugs are fixed. This helps those of us who are deploying and upgrading specific major versions in automated or containerized environments.

Take the below snippet from a Dockerfile for example:

FROM debian:11-slim AS base

ARG VERSION=2.19

ENV WEBWORK_URL="https://github.com/openwebwork/webwork2/archive/refs/tags/WeBWorK-${VERSION}.tar.gz" \
    PG_URL="https://github.com/openwebwork/pg/archive/refs/tags/PG-${VERSION}.tar.gz"

RUN mkdir /opt/webwork

WORKDIR /opt/webwork

RUN APT_BASE_PKGS="apt-utils ca-certificates curl debconf-utils lsb-release" && \
    apt-get update && \
    apt-get install -y --no-install-recommends --no-install-suggests $APT_BASE_PKGS && \
    curl -fsSL https://deb.nodesource.com/setup_16.x | bash - && \
    apt-get install -y --no-install-recommends --no-install-suggests nodejs

RUN curl -o webwork.tar.gz -fsSLO $WEBWORK_URL && \
    curl -o pg.tar.gz -fsSLO $PG_URL && \
    mkdir webwork2 pg courses libraries && \
    tar -xzvf webwork.tar.gz -C webwork2 --strip=1 && \
    tar -xzvf pg.tar.gz -C pg --strip=1 && \
    rm -f webwork.tar.gz pg.tar.gz && \
    cd /opt/webwork/webwork2/htdocs && \
    npm ci && \
    cd /opt/webwork/pg/htdocs && \
    npm ci

...

There have been some bugfixes merged into the main branch but, because there hasn't been a new tag, a new strategy has to be adopted in the Dockerfile to pull them in (e.g. curl -o webwork.zip -fsSLO https://github.com/openwebwork/webwork2/archive/${COMMIT_SHA}.zip).

[drgrice1]

This is unlikely to happen at this point or anytime soon. It does not fit our development cycle. Numerous hotfixes have been merged, and we aren't going to make a point release each time that we do this. Generally we don't have the maintenance infrastructure to handle this sort of thing.

At this point such deployments of webwork2 are quite rare. So this will be extremely low priority.

[somiaj]

Note, you can use the github api to download a .tar.gz of the current main branch directly vs using a release tarball. I just tested and this gets the current version of the main branch.

curl -L https://api.github.com/repos/openwebwork/webwork2/tarball/main > webwork2.tar.gz

Note the tarball extracts to openwebwork-webwork2-<last commit hash>, so in my testing it was openwebwork-webwork2-647d317.

[miralgj]

Fair and honest response. I will find a way to adjust my process.

Il giorno ven 20 set 2024 alle 3:17 PM Glenn Rice @.***> ha scritto:

This is unlikely to happen at this point or anytime soon. It does not fit our development cycle. Numerous hotfixes have been merged, and we aren't going to make a point release each time that we do this. Generally we don't have the maintenance infrastructure to handle this sort of thing.

At this point such deployments of webwork2 are quite rare. So this will be extremely low priority.

— Reply to this email directly, view it on GitHub https://github.com/openwebwork/webwork2/issues/2577#issuecomment-2364398251, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAPFJODAZZCLCI7AHUKSHDZXRYC3AVCNFSM6AAAAABOSROYHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGM4TQMRVGE . You are receiving this because you authored the thread.Message ID: @.***>