{"id":5541,"date":"2018-02-02T08:10:07","date_gmt":"2018-02-02T08:10:07","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=5541"},"modified":"2021-06-04T12:01:38","modified_gmt":"2021-06-04T12:01:38","slug":"the-month-in-wordpress-january-2018","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2018\/02\/the-month-in-wordpress-january-2018\/","title":{"rendered":"The Month in WordPress: January 2018"},"content":{"rendered":"\n
Things got off to a gradual start in 2018 with momentum starting to pick up over the course of the month. There were some notable developments in January, including a new point release and work being done on other important areas of the WordPress project.<\/p>\n\n\n\n
On January 16, WordPress 4.9.2 was released<\/a> to fix an important security issue with the media player, as well as a number of other smaller bugs. This release goes a long way to smoothing out the 4.9 release cycle with the next point release, v4.9.3, due in early February<\/a>.<\/p>\n\n\n\n To get involved in building WordPress Core, jump into the #core channel in the Making WordPress Slack group<\/a>, and follow the Core team blog<\/a>.<\/p>\n\n\n\n At the end of 2017, the guidelines for the Plugin Directory<\/a> received a significant update to make them clearer and expanded to address certain situations. This does not necessarily make these guidelines complete, but rather more user-friendly and practical; they govern how developers build plugins for the Plugin Directory, so they need to evolve with the global community that the Directory serves.<\/p>\n\n\n\n If you would like to contribute to these guidelines, you can make a pull request to the GitHub repository<\/a> or email plugins@wordpress.org<\/a>. You can also jump into the #pluginreview channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\nUpdated Plugin Directory Guidelines<\/h2>\n\n\n\n
\n\n\n\nFurther Reading:<\/h2>\n\n\n\n
\n