Author Archives: George Stephanis

George Stephanis 3:36 pm on November 28, 2013
Tags:   

The plugins repo is currently serving up the…

The plugins repo is currently serving up the 2.6.1b1 tag for Jetpack, but saying that it’s 2.6.

When you download the file and open it up, the changelog contained in the readme.txt file matches the 2.6.1b1 tag, not the 2.6 tag, or trunk (which it had glitched to previously a few months back).

Trunk’s current readme does point to 2.6 as the stable tag.

Today, on Thanksgiving, I’m thankful that this is just a minor bugfix point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. that slipped out early, and everything that changed in it should be safe and good to have deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.. However, users that upgrade to or install it via their dashboard, or download the zip are still getting told that it’s a beta release, which can certainly scare users.

cc: @otto42 @samuelsidler

I’m going to be trying to do whitespace commits to some of the readme.txt files, hoping to glitch it back to being correct again.

#plugin-directory

George Stephanis 7:20 pm on July 8, 2013
Tags: mu   

Not sure if something’s messed up on my…

Not sure if something’s messed up on my end or what, but for https://mu.wordpress.org/ I’m seeing

Source HTML: https://gist.github.com/georgestephanis/5951646

— just confirmed with @iandunn that it’s rendering properly for him, so I’m not sure if it’s just me?

#mu

George Stephanis 3:15 pm on June 3, 2013
Tags: ack, grep, opengrok   

So I had a thought the other week…

So I had a thought the other week.

How feasible would it be / would there be any interest in running an OpenGrok install for WordPress plugins? Perhaps at something like plugins.opengrok.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/?

It would make it a lot simpler to check for namespace conflicts with plugins, compatability questions, find usage details for APIs and filters, and it would save a goodly amount of time and hard disk space for anyone currently using @markjaquith‘s WordPress Plugin Directory Slurper (which eats over 4 gigs, takes hours to install, is a nuisance to keep updated, and takes forever to ack/grep through) (but is still far better than any current alternative).

The biggest difficulty that I can see is narrowing it down to scanning only the active branch, since some plugins keep an empty trunk folder, with just a readme.txt to point to the currently released branch. Unless it just scans an install of the slurper being run on an wporg server.

#ack, #grep, #opengrok