Closed jgriss closed 5 years ago
Files to include:
The run.bat/ run.sh files should be enough if they point to the correct releases of the docker images.
I now created the folder RELEASE and copied the run scripts into it.
The run scripts of the different release can then be named accordingly.
I close this now but you can reopen the issue if this is not what you envisioned.
@veitveit
GitHub has a release function and I think we should use it. But having this RELEASE folder to collect all files that we want to ship to the user is a very good idea.
@jgriss The github releases are (in theory) directly translated into separate docker images, so this should work without problems
Am Di., 14. Aug. 2018 um 10:08 Uhr schrieb Johannes Griss < notifications@github.com>:
@veitveit https://github.com/veitveit
GitHub has a release function and I think we should use it. But having this RELEASE folder to collect all files that we want to ship to the user is a very good idea.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ProtProtocols/IsoLabeledProtocol/issues/56#issuecomment-412790104, or mute the thread https://github.com/notifications/unsubscribe-auth/APEZhW_jyHPV7Mkj1mgIHUjOEuH9NeTMks5uQoWXgaJpZM4VwKOH .
-- |||/ (o o) ----ooO-(_)-Ooo----
Don't worry about life; you're not going to survive it anyway.
We should provide a single ZIP file for people to download as a
release
.This should ideally be done once all issues of a milestone are reached.