Updates from westi RSS Toggle Comment Threads | Keyboard Shortcuts

  • Peter Westwood 10:40 pm on November 23, 2009 Permalink  

    Next dev chat will be on Thursday 3rd December at the usual time of 9PM UTC. This weeks is skipped due to Thanksgiving.
    Please leave Agenda items on the post below: http://wpdevel.wordpress.com/2009/11/19/suggest-agenda-items-for-nov-26th-dev-ch/

     

    • Jane Wells 3:12 am on November 24, 2009 Permalink

      In light of Thanksgiving, I’m going to do a “thanks” post for the dev blog this week since there’s no dev chat. Thinking I’ll call out the people who’ve contributed a patch (committed) to core since 2.7 (this year, basically) and forum moderators (and forum participants who do a solid job of helping people in the support forums without the official moderator label). Since we all know what a manual and aggravating task it is to make a list of core contributors (we need a better system for this), people can use this post to leave comments to give props to people who go above and beyond helping users in the forums, and if you’ve had a patch committed this year, maybe check your Trac profile to see if you have an actual name and/or URL listed in your profile. Thanks.

      • demetris 10:57 am on November 24, 2009 Permalink

        Jane:

        http://op111.net/misc/wp-29-props

        It is to be used by whomever writes the release announcement for v2.9.

        (This is a temporary page, not visible in the website navigation, and I am not going to publish it properly. I’m just maintaining the list, so that it will be ready for the release announcement. Oh, and people can also edit the source, or just send me a message, if they have any corrections or additions.)

        • Jane Wells 2:25 am on November 26, 2009 Permalink

          @Demetris: How are you compiling this list? By hand or do you have a handy script around that is pulling from the props lines?

        • demetris 3:19 pm on November 26, 2009 Permalink

          By hand.

          But it didn’t take take that long. (With a browser that supports relational links and also keyboard shortcuts for relational links, so that I did not have to take my hands off the keyboard.)

      • Denis de Bernardy 7:15 pm on November 24, 2009 Permalink

    • Denis de Bernardy 6:08 pm on November 27, 2009 Permalink

      seems this needs discussion

      http://core.trac.wordpress.org/ticket/11258

  • Peter Westwood 10:31 am on November 21, 2009 Permalink  

    Should we skip this weeks dev chat because of Thanksgiving? 

     

  • Peter Westwood 9:55 pm on November 19, 2009 Permalink | Reply  

    Suggest agenda items for Dec 3rd dev chat

     

    • Matt Martz 10:01 pm on November 19, 2009 Permalink | Reply

      How do we handle security releases in the admin? If a user is running an old 2.8 such as 2.8.1 do we tell the user that 2.8.6 is available or 2.9? And when on 2.8.6 tell them that 2.9 is available? Or do we need to do another release in 2.8 to give us more UI capabilities so that we can tell the user that both 2.8.6 is available and 2.9?

      We covered this a little in the Dev chat for the 19th. Everyone think it over and come back with some ideas.

      I would like to see us start with 2.8, so we should get this figured out soon.

    • Daryl Koopersmith 6:55 am on November 20, 2009 Permalink | Reply

      We might want to reschedule this week’s dev chat since Thanksgiving is on the 26th for us Americans. Thoughts?

      • Matt Martz 3:19 pm on November 20, 2009 Permalink | Reply

        That is a good point. I will actually be travelling and not available for the meeting. I leave Wednesday and am not back until Sunday. I say move the meeting to Tuesday or maybe skip a week.

      • Peter Westwood 10:32 am on November 21, 2009 Permalink | Reply

        I have started a poll above to get some feedback

    • Denis de Bernardy 9:16 am on November 21, 2009 Permalink | Reply

      Re: http://core.trac.wordpress.org/ticket/10738#comment:5

      Imo, it is Appearance that should have been renamed back to Themes… I don’t know about others, but that one was one change to the UI that I did NOT find relevant (at all)

      • Peter Westwood 9:20 am on November 21, 2009 Permalink | Reply

        I think this is better discussed on the ticket rather than in the meeting – do you want to comment there.

      • Dre Armeda 5:11 pm on November 21, 2009 Permalink | Reply

        Denis, I think Appearance is appropriate but there are other items I would like to see added. I commented on the ticket.

      • Jane Wells 6:45 pm on November 23, 2009 Permalink | Reply

        Added my comment to trac late, so repeating here. Was renamed Appearance b/c so many people got lost looking for widgets, which regular people don’t associate with themes. We can address possible re-naming in 3.0, when we’ll address menus (with merge) and header/nav touch-ups (postponed from summer).

        • Matt 7:10 pm on November 23, 2009 Permalink

          Good point on Widgets, I had forgotten about that.

        • Denis de Bernardy 8:26 pm on November 23, 2009 Permalink

          The point on docs is much more compelling imo. It’s end of story, even. ;-)

        • Lloyd Budd 6:43 pm on November 27, 2009 Permalink

          @jane > we’ll address menus (with merge) and header/nav touch-ups
          Link to more info? Would be good in the tic too.

    • Denis de Bernardy 9:18 pm on November 21, 2009 Permalink | Reply

      Create a post on the wp.org dev feed that highlights what breaks to plugin devs. And do so with every release.

      My own tests didn’t reveal much that broke with 2.9 except for the new trash status. Then again I’m sure I’m missing things since I’ve no plugins that mess around with comments.

      Anyway, the point would be to highlight what breaks and why in language that plugin devs can understand. In the case of the new trash can, it means something like:

      WordPress’ new Trash feature introduces as new post status, and a new comment status. Contrary to revisions in WP 2.6, which had introduced a new post type, this new “trash” status has the potential to break plugins.

      Yours might be broken if it uses direct SQL queries with no constraints on the post or comment status field, such as:

      http://core.trac.wordpress.org/changeset/12254

      yada, yada…

      • Denis de Bernardy 9:19 pm on November 21, 2009 Permalink | Reply

        Adding to the previous comment, there might still be other queries in WP that might need to be looked into.

  • Peter Westwood 8:30 pm on November 19, 2009 Permalink | Reply  

    Agenda for Nov 19th Dev Chat 

    Agenda for Nov 29th Dev Chat
    * 2.9 beta status review – mark/ryan/andrew/peter
    * Patch backlog – demetris
    * Page Templates in subdirs – peter
    * WPMU Compatibility – sivel

     

  • Peter Westwood 9:51 pm on November 12, 2009 Permalink | Reply  

    Suggest agenda items for Nov 19th dev chat

     

  • Peter Westwood 8:50 pm on November 12, 2009 Permalink | Reply  

    Agenda for Nov 12th Meetup
    * 2.9 status – Ryan/Andrew/Peter/Mark
    * Plugin Compatibility – Aaron
    * Minimised css/js – scribu
    * FOSDEM developer room – Nikolay

    * security functions – Mark Jaquith

     

    • Weston Ruter 11:04 pm on November 12, 2009 Permalink | Reply

      Regarding minimized JavaScript, I’ve been working on a plugin that automatically concatenates scripts and compresses them using Google’s Closure Compiler. Here’s the work in progress: http://gist.github.com/233399

      Perhaps scribu has already finished what I’ve been working on, but in any case, I wanted to alert you to my related project.

  • Peter Westwood 10:02 pm on November 5, 2009 Permalink | Reply  

    Suggest agenda items for Nov 12th dev chat

     

    • Aaron D. Campbell 6:26 am on November 7, 2009 Permalink | Reply

      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.

    • arena 7:20 am on November 9, 2009 Permalink | Reply

      WordPress 3.0 blueprint !

      • Peter Westwood 8:49 pm on November 12, 2009 Permalink | Reply

        I think this needs to wait until a later date when we have got the 2.9 beta program in full swing.

    • scribu 7:18 pm on November 9, 2009 Permalink | Reply

      Possibility of removing minimised .css and .js from source control.

      • Alex M. (Viper007Bond) 10:18 pm on November 9, 2009 Permalink | Reply

        Don’t forget that not all server configurations support the minifying on the fly.

        • scribu 10:55 am on November 12, 2009 Permalink

          The server that generates the nightly builds is enough. ;-)

          But we’ll talk more about that at the meeting.

    • Nikolay Bachiyski 10:58 am on November 12, 2009 Permalink | Reply

      See if there are enough interested people to reserve a developer room at FOSDEM.

  • Peter Westwood 8:52 pm on November 5, 2009 Permalink | Reply  

    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 5:59 am on November 6, 2009 Permalink | Reply

      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.

  • Peter Westwood 10:29 pm on October 29, 2009 Permalink | Reply  

    Suggest agenda items for Nov 5th dev chat

     

    • Bryan 10:03 pm on October 31, 2009 Permalink | Reply

      Need fresh patch for inline documentation corrections. http://core.trac.wordpress.org/ticket/6362

    • Nicolas Kuttler 1:18 pm on November 3, 2009 Permalink | Reply

      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 1:26 am on November 5, 2009 Permalink | Reply

        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 7:02 am on November 5, 2009 Permalink

          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 1:27 am on November 5, 2009 Permalink | Reply

      Bug hunt /patch testing sprint Nov 5-7. ID who will be on to review things for commit, etc.

    • Peter Westwood 8:16 pm on November 5, 2009 Permalink | Reply

      Discuss “Discourage plugin authors calling wp-config.php directly” –
      http://core.trac.wordpress.org/ticket/11059

  • Peter Westwood 8:58 pm on October 29, 2009 Permalink | Reply  

    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

     

Older Posts →

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
esc
cancel