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

Upload updated Excel Template V021 with new Read-Me table #65

Closed

Conversation

Maja4Dev
Copy link
Collaborator

Updated Excel Template Version EN V021 of 24.05.2024 which is consistent with updated Technical Notes (= Excel table READ-ME).

Updated Excel Template Version EN V021 of 24.05.2024
@Maja4Dev Maja4Dev linked an issue May 24, 2024 that may be closed by this pull request
@Maja4Dev Maja4Dev assigned Maja4Dev and Jo-Schie and unassigned Maja4Dev May 24, 2024
@Maja4Dev
Copy link
Collaborator Author

After upload, the links to this template on the other pages have to be changed so that they link to this new version.

Copy link
Collaborator

@fretchen fretchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be much better to really update the excel template and not do versioning within the file name.

The advantages are:

  • No links need to be updated.
  • We have a clear track record of the changes to the document (all within git records).

The file name is really a very poor place to keep the version as it is constantly changed by users. Better ways for versioning:

  • If you want to have a note of the version in the excel file (which might be a good idead), it might be best noted in a specific excel sheet, which describes the history.
  • As soon as the tasks for the milestone of v1 are fulfilled we can do a release where the how documents including templates are tagged as release v1.

So I would strongly recommend to change the filename such that it overwrites the old file.

@Jo-Schie
Copy link
Collaborator

It would be much better to really update the excel template and not do versioning within the file name.

The advantages are:

  • No links need to be updated.
  • We have a clear track record of the changes to the document (all within git records).

The file name is really a very poor place to keep the version as it is constantly changed by users. Better ways for versioning:

  • If you want to have a note of the version in the excel file (which might be a good idead), it might be best noted in a specific excel sheet, which describes the history.
  • As soon as the tasks for the milestone of v1 are fulfilled we can do a release where the how documents including templates are tagged as release v1.

So I would strongly recommend to change the filename such that it overwrites the old file.

Sounds very logical to me. I would suggest adding a new tab "version and changelog" where we track the changes to the model also verbally within the model.

@fretchen
Copy link
Collaborator

fretchen commented Jun 8, 2024

Was made redundant by #66

@fretchen fretchen closed this Jun 8, 2024
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 this pull request may close these issues.

Upload updated Excel Template EN with new Read-Me
3 participants