fresh fruit for rotting vegetables

new year, new blog, old name for WordPress developers

January 10, 2020 — ~boogah

On the WPwatercooler podcast this week — while talking about what's coming in 2020 — I proposed that WordPress plugin developers might want to consider adding files to their GitHub repos.

Much like shows you where a project has been, would show you where a project is headed.

  • Planning on fixing a long-standing issue? Put it in
  • Working on a new feature? Put it in
  • Getting ready to roll out indexes for common database queries? Put it in

Standard changelog rules apply. Group things by version number, with simple, digestible bullet points. Add context where necessary. Avoid putting dates on things so you're not on a deadline.

Unlike changelogs, which are kept in reverse-chronological order, roadmaps should be kept in chronological order. What's coming up in the next release should be the first thing people read. You don't want to make your users dig around for what's next, do you?

Should anyone decide to do this, I'd love to know about it. At me on Mastodon or Twitter and send me a link to your repo!

tags: wordpress, roadmap, changelog