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

Version Specific Release Type Tags #462

Closed
mbax opened this issue Feb 28, 2018 · 8 comments · May be fixed by #949
Closed

Version Specific Release Type Tags #462

mbax opened this issue Feb 28, 2018 · 8 comments · May be fixed by #949

Comments

@mbax
Copy link

mbax commented Feb 28, 2018

Would be nice to be able to send from a selectable list the type of release a file is.

  • Bug fix
  • New feature
  • Security fix

That way, you could have plugins query this when checking for updates and alert if there's a security fix as a file between the current version and latest.

@phase
Copy link
Contributor

phase commented Feb 28, 2018

To be more specific, you're proposing we have tags notating what "type of release" a specific version is.

This could be another section of tags on the versions page.

@phase phase changed the title "Type of release" data on file Version Specific Release Type Tags Feb 28, 2018
@codeHusky
Copy link

being able to attach specific bits of information to why things are tagged as they are so the server admins can decide in game when they want to update would be best.

Sure this is "abusable" but it's just as abusable as any other part of release data.

@phase
Copy link
Contributor

phase commented Feb 28, 2018

You're saying linking to, say, a blog post on what security issues were fixed would be helpful? I think that's a good idea. We already have a release post generated when you create a new version, and we could have a textbox (if it doesn't already exist (pardon my misremembering of the version creation screen)) that would be appended to the release post, and their can be a link to it from the tags mentioned. This sound good?

@codeHusky
Copy link

It's more so that it's easy for plugins to pull from the data and present to server admins so they know why they should update, not just that they should

@felixoi
Copy link
Member

felixoi commented Feb 28, 2018

@codeHusky Correct me if I misunderstood this:
You wanna have a release type as mentioned before with a optional description? So you can include the description if you do a security fix, then you fetch the lastest version from the API, check if it's a security fix and warn the server admins that there is a security fix and you display the description.

@codeHusky
Copy link

Display the details of the security fix specifically, yeah.

@mbax
Copy link
Author

mbax commented Mar 1, 2018

Can I get an example scenario where there's a benefit to the user in showing them the nature of the security fix in game or in console, over just noting it's a security fix (and thus high priority fixing) and directing to the Ore page for details?

@codeHusky
Copy link

Release is out for a big dupe bug via a plugin. Owner runs a survival server and would prefer not to restart. They are notified of the exploit via the nature being notified to them and immediately update to prevent damage to in game economy.

@Katrix Katrix added the component: tags New Tag or having to do with the Tag System label Jan 11, 2019
@Katrix Katrix added this to the v1.8.x milestone Feb 16, 2019
@Katrix Katrix modified the milestones: v1.8.x, v1.8.5 May 6, 2019
@Katrix Katrix modified the milestones: v2.0.1, v2.0.0-M3 Jan 26, 2020
@Katrix Katrix mentioned this issue Apr 23, 2020
@Katrix Katrix closed this as completed Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants