SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am the slackbuild maintainer for warzon2100 and have been questioning which releases I should prepare and submit to slackbuilds.org, I would like you input.
My current process is to only test non-beta releases and submit the new builds after each version has been tested for at least 2 weeks to guarantee stability. I would like to know if the users would prefer to get the beta releases and all versions promptly or if you prefer the current testing/release criteria.
Awesome! However, I see the slackbuild is for ver 2.3.8, which is unsupported.
I know its a lot to ask, but if you could provide slackbuilds for a) stable version and b) most recent beta version, that will give you the needed input on how stable the beta release is, while giving users a stable version at the same time. I'm sure theres some people out there who'd like to try the latest stuff out.
The current state of warzone is what caused the question, the latest stable is 2.3.9 which is unsupported, however the only supported versions are beta quality.
I know that I cannot request for both the stable and unstable versions to be hosted on slackbuilds, but I can do both in my github repo and submit only the stable updates to slackbuilds.org. Would that solution work for you?