jQuery Updater was one of the very first WordPress plugin I`ve wrote, and was released in April 2011. During that time jQuery was hot.
My plugin allowed users to use an updated version of jQuery, either bugfix release or minor release not originally bundled with WP.
Nowadays jQuery`s releases are ocasionaly, with the last one 10 months ago. This means the plugin hasn`t been updated for the same time.
Also the userbase of my jQuery Updater for WordPress plugin is shrinking.
WordPress 4.9 comes standard bundled with jQuery 1.12.4
Using jQuery 2 or 3 with this version will surely cause issues with the WP bundles scripts.
This directly leads to low star ratings and bad reviews.
Several years ago I started a branch to increase the functionality and add a user interface to the plugin. By now nothing more happend to the source code than a lot of placeholders and unfinished items.
All this together with my lack of time, I`ve decided to halt further development of the plugin until further notice.
This means I will do minor patches within jQuery 3, but without significant changes to the plugin other than updates.
Today I`ve finished laying the engine foundation for jQuery Updater for WordPress 3.0
The release of jQuery 3.0.0 alpha 1 triggered me to swap from 2.1.4-beta to 3.0.0-alpha but I`m happy with it. The plugin`s engine got completely rewritten and includes some code that I used to maintain seperatly as a plugin; jQuery Mobile, but also includes jQuery UI and QUnit.
Today I`ve started working on my jQuery Updater for WordPress plugin.
Step 1: moving to GitHub
First step was linking Subversion and Git, which was a hell
Step 2: decide workflow
The second step is deciding the workflow: tools and rules. I decided to skip Grunt and Vagrant for now, since the code isn`t going to be rocket science.
I use phpDoc for documenting the PHP code and GitHub as project management (issues, milestones).
This setup will do fine for now!
Step 3: project management
Making a roadmap, with issues, features and prioritising all that I want before I start working and losing grip on the project.
Step 4: work
Starting with cleaning up code followed by creating space for new features. Leaving the hardest bits for the last. Although this isn`t ideal it makes future development a whole lot easier.