Suggest agenda items for Nov 12th dev chat
Recent Updates RSS Hide threads | Keyboard Shortcuts
-
Peter Westwood
-
Peter Westwood
Agenda for Nov 5th Meetup
* Plugin compatability and default tag – Nicolas Kuttler
* Bug hunt – Jane
* “Discourage plugin authors calling wp-config.php directly” – Peter
* proposed structure for release announcements – demetris
* Improved Hello World post – demetris
* Status for 2.9 beta readiness-
Mark Jaquith
Plugin compatability and default tag – Nicolas Kuttler
Michael Adams informs me that this fix has been pushed and that the current stable version will be the default, instead of the most recent tag.
-
Nicolas Kuttler
That’s great! Thanks Michael for fixing it so quickly!
-
-
-
Peter Westwood
Suggest agenda items for Nov 5th dev chat
-
Bryan
Need fresh patch for inline documentation corrections. http://core.trac.wordpress.org/ticket/6362
-
Nicolas Kuttler
The plugin compatibilty beta shows all tags that exist. This is fine, but I think it should select the latest stable tag by default, not the newest that exists. I like to tag experimental versions and versions for translators, but for 99.9% of all visitors only the compatibility of the latest stable release is relevant.
(If 0.1 is stable and there is a 0.1.1 it will be displayed instead by default)
-
Jane Wells
I think people assume the most recent version number is the stable one they should be using, since that is how WordPress itself works. The default should be the most recent on both menus for a consistent experience. Is something isn’t stable, maybe it doesn’t belong in the repo yet?
-
Peter Westwood
This is not quite the case. The readme.txt format allows the plugin author to say which is the stable tag and that is what is presented as the latest version for download.
That should be the default version in the dropdown
-
-
-
Jane Wells
Bug hunt /patch testing sprint Nov 5-7. ID who will be on to review things for commit, etc.
-
Peter Westwood
Discuss “Discourage plugin authors calling wp-config.php directly” –
http://core.trac.wordpress.org/ticket/11059-
demetris
1. I have drafted a proposed structure for release announcements (as I promised in the last meeting)
2. If there are time slots left, I would like to see some feedback on the new Hello World post: http://core.trac.wordpress.org/ticket/11008
-
-
-
Jane Wells
Note to self: schedule bug hunts/patch testing sprints for Sun-Mon a week from now and Thurs-Sat in mid-November, per IRC dev chat today. Announce on dev blog tomorrow.
-
Peter Westwood
Agenda for Oct 29th dev chat:
* Custom post type ui – Lari
* Security only patches – Beau
* Beta readiness – westi
* Memory requirements – Jeffro
* Update announcement improvements – demetris -
Peter Westwood
Suggest agenda items for Oct 29th dev chat
-
Lari
Custom post type ui. Can it make it to 2.9?
-
Alex M. (Viper007Bond)
2.9 is feature frozen.
-
-
Beau
Doing security-only patches as a way of 1. maintaining some level of support for older versions of WP, and 2. being “safer” to implement fully-automated core upgrades
-
Alex M. (Viper007Bond)
Isn’t that what was done with the 2.0.x branch? Turned out to be a ton of work and not really worth the trouble.
http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/
-
-
Peter Westwood
Review status of features with regard to beta readiness
-
Jeffro
I’m noticing more and more with queries in the WordPress support forums of folks who upgrade WordPress only to be greeted with memory limit exhausted errors. I had this problem myself when I upgraded to the version of WordPress once SimplePie was used as the feed parser. I had to go from 32 megs to 64. Is it possible that this information needs to be added to the minimum requirements page on WordPress.org? http://wordpress.org/about/requirements/
-
Matt Martz
I think one thing that people tend to forget is that they should deactivate all plugins before performing an upgrade. Did you perform this step when you did the upgrade? Maybe what we should do is detect whether or not plugins were deactivated. If not, then make a backup of the option containing the active plugins, clear the option, upgrade, then restore it. Or perhaps add a check to see if we are upgrading and then not load plugins if that constant is set. Just some ideas.
-
demetris
Deactivating plugins before upgrading is good advice in theory, but in practice it is problematic, since very often plugins offer functionality that is integral to a site. You can’t just deactivate them.
For upgrade issues caused by plugins, another idea would be to have a “Known Issues” part in the release notes. If a prominent, popular plugin breaks something essential in WordPress when upgrading (and WordPress has enough prerelease testers to catch such issues for popular plugins), then it could be mentioned as a Known Issue.
-
Eric Marden
@demetris
Is that what .maintenance is for? http://sivel.net/2009/06/wordpress-maintenance-mode-without-a-plugin/
-
-
-
demetris
1. Improve template for new release announcements
2. Link to release announcement from admin upgrade notice, something like: [Read what is new] or [Click to upgrade]
-
-
Matt
I updated the access flags for #wordpress so more people can help out there when there is trouble. To remind folks, our policy is for people not to be “opped” all the time, only when needed to set/change things. Here are the new folks with access:
sivel
Viper007Bond
bazza
MarkJaquith
Ozh-
Mark Jaquith
I wasn’t up on ChanServ… appears that op/deop works like this:
- /msg ChanServ OP #wordpress
- /msg ChanServ DEOP #wordpress
-
Matt
Thanks Matt! I have cleared out all of the old outdated bans, and set a few new modes on the channel. If anyone has any questions about the commands and such feel free to ask me on IRC.
-
-
Peter Westwood
Agenda for Oct 22nd dev chat:
- Additional non-oembed sites – Viper007Bond
- Upgrade notification in core
- Trac voting
- Multiple custom image sizes with retroactive image reprocessing – Scribu
- Mailing lists
- #WordPress ops
- Trac configuration -
Ryan
Prepping 2.8.5. Get the beta here.
Changes:
- Fix for trackback DOS
- Removal of permalink_structure eval
- Remove some create_function() calls
- Disallow unfiltered uploads for admins by default. Enable it again with define(‘ALLOW_UNFILTERED_UPLOADS’, true); in wp-config.php
- Add extra escaping here and there for defense in depth
- Retire two old importers
- A few small bug fixes
This is mainly a security hardening release done as part of our always ongoing security audits. There’s nothing exciting in here unless you are concerned about the trackback DOS bug.
-
Jonathan Dingman
Keep up the great work Ryan! Good job on the fast and responsive release to the threat (even though in my mind, not a serious one).
-
hakre
Well it was about time for some of those
. But it’s good to see them finally in!
Peter Westwood
Suggest agenda items for Oct 22nd dev chat
-
Alex (Viper007Bond)
I’d like to hear any suggestions for additional non-oEmbed sites that people would like to see supported.
-
Bryan
It would be nice if oEmbed was backwards compatible with Viper’s Video Quicktags or any number of similar plugins that use shortcodes such as: [youtube] [/youtube]. Otherwise plugin-dependent users will not be able to utilize the native oEmbed features without re-editing many posts.
-
Alex M. (Viper007Bond)
As mentioned on my blog, WordPress can’t be expected to handle the infinite number of video related shortcodes out there. It’s up to plugins to create a bridge.
-
-
-
scribu
Set up an official poll: Upgrade notifications by mail into core.
It’s being discussed in wp-hackers, but with no conclusion.
-
JeffC
I would like to know if the up and down arrow votes for a ticket in Trac has any effect in terms of priority or attention it receives?
-
scribu
Multiple custom image sizes with retroactive image reprocessing (Ticket #8599)
-
Massalha Shady
Hi, WP 2.8.5 Still slow. I spent a lot of time trying to fix it but with no success. And please, dont say plugins/mlugins, i have deleted all plugins – reset it – and Dashboard still SLOW??!?!? This is the pacth we need ASAP. because WP is great and have to continue that …
-
hakre
I would like to see the PHP upgrade information finally in. It looks pretty ready to me: (Ticket #9751) and should fit nice to take more care for the users security.
-
Matt
I’d like to discuss creating a new mailing list where the non hackers on the wp-hackers mailing list can take their discussions to. The name of the list doesn’t matter so much, Andy recommended wp-discuss. See this thread on wp-hackers for more information:
http://lists.automattic.com/pipermail/wp-hackers/2009-October/028097.html
-
Jeffro
This has been a long time coming. There is no place to discuss general information or ideas for WordPress. There is the ideas section but nahh, I’d like to see a mailing list just for feedback and discussion on topics or ideas. So I +1 for wp-discuss
-
-
Matt
Meeting Task: #wordpress OPs for sivel and Viper007Bond If Matt is in attendance
-
Jeffro
Persistence will pay off eventually
-
-
hakre
I would like to have the xmlrpc interface in wordpress core trac use the eclipse mylyn trac connector via xmlrpc. Currently I need to use SSL (mainly for auth) and that is slow (and I think it eats server resources). This is a nice system for an upcomming patch-run if anyone is interested for eclipse/wp infos, checkout my codex page.
Aaron D. Campbell 6:26 am on November 7, 2009 Permalink |
On the 5th we talked about “Plugin compatability and default tag” specifically that the default selected option should be the current stable version. I see that now the beta (2.9) doesn’t show at all. I’d like to see if we could add beta versions to the dropdown, and just make the current stable release the selected option.
Aaron D. Campbell 6:29 am on November 7, 2009 Permalink |
Sorry, the last discussion was on the plugin version. I’m talking about the WordPress versions. I see 2.8.4 and 2.8.5 as the WordPress version choices right now: http://wordpress.org/extend/plugins/mailchimp-framework/