Closed theopolisme closed 11 years ago
Similar note: @Nathan2055, can you explain these? Seem like clutter to me, since our current strategy is just "push to master" == "release", "push to beta"* == "beta", "push to develop" == "alpha".
*This reminds me, maybe create another branch, beta
, that will sync with a beta gadget on-wiki?
+1
Sure. Which branch should we push, and where should it be pushed to? Someone should create a "beta" branch from develop's current HEAD and use that. In the past we've used User:Mabdul/afc_beta.js, should we continue using it? Or a page in the MediaWiki: namespace? Note that src/afch.js currently hardcodes the path "MediaWiki:Gadget-afchelper.js", but I can have the deployment script change that.
Here's the beta branch: https://github.com/WPAFC/afch/tree/beta MediaWiki:Gadget-afchelper-beta.js seems more consistent to me, but we could leave it in userspace if needed.
Done!
@theopolisme - I created those because I had wanted ways to access the repo as it was during a specific build. It would be better just to use master
and beta
--no-ff merges, though.
Could you delete them, then?
@theopolisme - Sure, but I'm going to need to figure out how to delete tags.
{{done}}
@legoktm most "beta tester" will actually have my afc beta.js file in their vector/monobook skin included; I think we should stay there!
@wikipedia-mabdul - I can fix that with a few protected edit requests.
Looking at the issues page, we currently have no critical issues and no bugs -- only enhancements of varying intensity. Per (most recently) this and other threads on-wiki, I think it's time for us to get ready to release a version of the script for beta testers to use and test. @legoktm has the mechanism for updating the gadget files written, so I'd like to advocate for a "beta" release in the coming days. Thoughts?