Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2548380dbb22877

Jump to content

Wikipedia:AutoWikiBrowser/Dev

From Wikipedia, the free encyclopedia

How to release a new version

[edit]
  1. Double-check everything, including Fandom (previously Wikia) support if at all possible.
  2. SVN update working copy to latest (Right click on AWB source folder in Windows Explorer and use Tortoise SVN -> SVN update, or use svn up on a command line).
  3. Increment the AutoWikiBrowser and WikiFunctions Versions to the release versions, and update the copyright years if appopriate: ..\AWB\AWB\Properties\AssemblyInfo.cs and ..\AWB\WikiFunctions\Properties\AssemblyInfo.cs e.g. rev 13020. If appropriate, update the copyright years in ..\AWB\WikiFunctions\Resources.resx (the "GPL" resource) and the comment in ..\AWB\WikiFunctions\Resources.Designer.cs. Then commit.
  4. Do a release build in Visual Studio or SharpDevelop.
    • In Visual Studio: load AutoWikiBrowser.sln, select Release and press F6. Run the unit tests. Then load Extras\Extras.sln and press F6.
    • In SharpDevelop: Select Build → Set configuration → Release and then press F8 to build solution.
  5. Run the AWBPackager in Extras to build the zip to be uploaded. Use option 2.
  6. Even if you have an antivirus running, use a virus checker to make sure that the zip file is 100% virus-free.
  7. Log in to SourceForge project; you need admin rights for the project.
  8. Click to files, click to "autowikibrowser" folder.
  9. Add a new folder AutoWikiBrowserXXXX (XXXX = version, matching zip file name).
  10. Click to the folder you just created, upload the zip file.
  11. Edit the properties of the file (use i icon) to set it as the default release for all platforms.
  12. Wait a minute or two and the SourceForge pages should refresh to show the new release as the latest release at summary.
  13. Add the version to AWB's Wikidata entry. Using the existing entries as a model, make the new version "preferred" and downgrade the previous version. This will cause Wikipedia:AutoWikiBrowser/CurrentVersion to be updated.
  14. Now, decide whether to tag the release in SVN.
    • On AWB folder in root of working copy choose Tortoise SVN -> branch/tag.
    • Fill in path to be as \tags\REL_X_X_X_X to match release version.
    • Execute this and a new tag will be committed to repo.
  15. Finally, update the AutoWikiBrowser and WikiFunctions versions again, adding .1 to the fourth fields, and commit this back to the SVN as a version bump e.g. rev 8982.

Update AWB Pages

[edit]
  1. Visit Wikipedia:AutoWikiBrowser/CurrentVersion, and verify it shows the current version.
  2. Visit Template:Latest stable software release/AutoWikiBrowser and set release date.
  3. Visit Wikipedia:AutoWikiBrowser/History and update the history for this release. If there is a commented-out interim list, restore it.
  4. If you are an admin visit Wikipedia:AutoWikiBrowser/CheckPage/VersionJSON, or if not, get an admin to, and update the enabledversions object. Add the new version with the release date, and "released" true; add the "bump" version with "dev" true, as here. You can also force an update from old versions by removing them from the table.