Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Unify releases for all advanced modules #45

Closed
programming-wolf opened this issue Feb 5, 2020 · 2 comments
Closed

Unify releases for all advanced modules #45

programming-wolf opened this issue Feb 5, 2020 · 2 comments

Comments

@programming-wolf
Copy link
Collaborator

programming-wolf commented Feb 5, 2020 •
edited
Loading

The template should provide an explanation/documentation on how the module releases should be named.

One possible definition could be MODULE-YEAR, e.g. WEB-2020. Smaller fixes to the module curriculum could be highlighted with an additional number, for example WEB-2020.1 or WEB-2020 rev2`.
@aheusingfeld aheusingfeld mentioned this issue Mar 6, 2020
Open
@programming-wolf
Copy link
Collaborator Author

Current idea/approach: YEAR.VERSION-revREVISION.

@programming-wolf
Copy link
Collaborator Author

The approach as described in my previous commit was accepted and is already used with several modules.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@programming-wolf