Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrapper script doctoolchain.github.io/dtcw still uses v.2.1.0 #1030

Closed
mh182 opened this issue Feb 20, 2023 · 2 comments · Fixed by #1041
Closed

Wrapper script doctoolchain.github.io/dtcw still uses v.2.1.0 #1030

mh182 opened this issue Feb 20, 2023 · 2 comments · Fixed by #1041

Comments

@mh182
Copy link
Collaborator

mh182 commented Feb 20, 2023

Following the installation instructions as described in Install docToolchain.

To Reproduce
Steps to reproduce the behavior:

  1. Install docToolchain wrapper
➜  curl -Lo dtcw doctoolchain.github.io/dtcw
➜  chmod +x dtcw
  1. Check environment by calling the wrapper script
➜ ./dtcw 

dtcw - docToolchain wrapper V0.36
docToolchain V2.1.0
docToolchain as CLI available
docker available
home folder exists
No valid argument(s) supplied

Expected behavior
I would have expected the current release v2.2.0.

@rdmueller
Copy link
Member

yes, it is still on v2.1.0 because I wanted to wait one week to see if those who upgrade their scripts run into problems.
Do you think we should already by now change it?

@mh182
Copy link
Collaborator Author

mh182 commented Feb 21, 2023

If this was meant to be a delayed release of the wrapper script we may close the issue.

I was just surprised that after the installation of dctw it didn't use the latest release. I understand your reasoning but maybe other users will also be surprised as I was.

IMHO delaying the release of the wrapper script has more disadvantages than advantages:

  • It confused new users and the tracker may get similar bug reports like mine
  • What do we do if the new release fixes some bugs in the dctw?
  • It shows that the people working on the project do not have the confidence in the software quality they produce.

I would rather suggest to focus for fast bug-fix release in case a "paper bag error" (Papiersackerl Fehler) shows up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants