Make WordPress Core

Updates from Andrew Nacin Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 11:11 pm on November 21, 2012 Permalink
    Tags:   

    The short road to 3.5 

    Good dev chat today. The plan is for RC1 tonight (more on that in a moment). Here’s the current assignments for who is working on what, based on the main 3.5 report. Feel free to help with testing and patching across the board.

    • A number of IE7/8/9 issues with media, of varying severity. A number of people are working on this, and more are welcome. The focus is currently IE9 and IE8. Until those are fully working, IE7 should be untouched, as we may just severely degrade the media UI in IE7. #22446
    • Mark Jaquith is working on the SimplePie/DOMDocument/kses ticket. #21990
    • Dion was to work on the get_home_path() ticket, which is now fixed. #20449
    • The general IE audit for 3.5 was done with one more commit. #22467
    • The about page and feature pointers need an initial commit. #22455, #22454
    • The help text changes need a final review and commit. #22451
    • The WP_Image_Editor architecture ticket is still an ongoing conversation between scribu, Marko, and Mike Schroeder. #22356
    • Dominik (ocean90) has a patch ready to close out the attachment post type UI ticket. #21391
    • Koop is working on the media upload tickets. #22243, #22480

    Ongoing things:

    • The Tumblr Importer needs beta testers! It now uses their OAuth API, which requires you to create a (simple) app. Link to the beta version. #22422
    • Want to test WordPress 3.5? Consider testing the more interesting scenarios: mobile devices, desktop browsers (IE!), right-to-left languages.

    Lower priority tickets:

    • westi is working on the _wp_translate_postdata() ticket. #22417
    • The media tickets here will be worked on over the next few days. #22524, #22282, #22494, #22532 #22512, #22517
    • The child theme installation bug is now fixed in trunk. There is a patch with some additional error handling. #22515

    Decisions reached:

    • Twenty Ten will not be shipped with fresh downloads of WordPress 3.5. It will still be supported (and still reside in core SVN) and will continue to receive updates through the themes directory. #22500

    Schedule from here on out:

    • Release Candidate 1 today, once we have no more tickets of major severity open.
    • Eat turkey tomorrow. I won’t be opening my computer tomorrow. If you’re with family, you shouldn’t either.
    • Release Candidate 2 on Monday. At this point, report/6 should ideally be empty (no tickets). WordPress.com is also planning to merge 3.5 on Monday, which should significantly increase our test coverage (and bug reports) for media come next week.
    • Release Candidate 3 (assuming there are major bugs fixed after 2) no later than Monday, December 3.
    • Which sets us up for a December 5 release, assuming we don’t reach a critical mass of critical issues next week.

    [IRC logs]

     
    • pavelevap 12:21 pm on November 22, 2012 Permalink | Log in to Reply

      Hmm, what about string freeze? I saw some HUGE i18n commits last night and also About page is not ready. If I remember correctly, there should be at least 3 weeeks available for translators?

      • Andrew Nacin 1:38 pm on November 22, 2012 Permalink | Log in to Reply

        I tried to go easy on the i18n commits. About page is nearly ready. Strings will be formally frozen in the next 24-36 hours. You’ll have 12 days of freeze including two weekends (which is about our standard time for string freeze).

  • Andrew Nacin 7:08 pm on November 14, 2012 Permalink
    Tags: ,   

    Today’s dev chat, starting in two hours:

    • Triage http://core.trac.wordpress.org/report/5. No ticket should be without an owner, a path forward, and a timeline.
    • Discuss timeline for RC1 and how we are all feeling.
    • Things we need to do (or start thinking about) to prepare for a final release:
      • We need an About page of features. So, what are our wins?
      • Full sweeps for RTL, help text, IE, no JS, the blue color scheme, performance regressions, and 100% passing unit tests.
      • Continue to scan the support forums and awaiting review tickets reported against trunk to ensure we don’t miss anything.
      • Brainstorm what features and API changes need written tutorials (the “field guide”), and get people on board to research and write them.
      • Figure out what changes might need “3.5 compat” posts. The wpdb::prepare() argument change comes to mind, and obviously parts of media.

    All tickets should have people responsible for them, but also, so should all of these release preparation tasks. There’s something in there for everyone — bug gardeners, documentation, research, testing, etc.

     
  • Andrew Nacin 5:14 pm on November 7, 2012 Permalink
    Tags: ,   

    Dev chat is moving from 2000 UTC to 2100 UTC, as daylight saving time has gone into affect in both the US and UK. This keeps the meeting at 4 PM U.S. Eastern (a little under 4 hours from now).

    Agenda for today is to shore up http://core.trac.wordpress.org/report/6 and ready another beta to be kicked out the door.

     
  • Andrew Nacin 7:53 pm on October 31, 2012 Permalink
    Tags: , bug scrub   

    We’re going to do a bug scrub in lieu of a dev chat today. Starts in 7 minutes. (Most core developers still together for the WordPress Community Summit, and we’ve been doing quite a bit of chatting already…)

    Let’s aim to resolve/triage/punt a significant amount of report/6 in preparation for a beta.

     
  • Andrew Nacin 9:21 pm on October 23, 2012 Permalink
    Tags:   

    WordPress.org will be undergoing some maintenance starting Wednesday, October 24, at 11AM Eastern (1500 UTC), which will result in intermittent downtime (physical servers are being moved) over the course of a few hours. (This post originally said Tuesday, October 23, because I wasn’t paying attention to what I was typing.)

    Ideally, api.wordpress.org and the wordpress.org website (including this blog) will not go down, but access to all Trac installs and SVN repositories will be interrupted at some point. The goal is for error messages to be shown.

    I will update this post once the migration is complete.

     
  • Andrew Nacin 3:27 pm on October 17, 2012 Permalink
    Tags:   

    Suggest items for today’s dev chat.

    chat.freenode.net, #wordpress-dev, 20:00 UTC

    This will likely be a working meeting. Let’s push through and line things up for beta 3.

     
  • Andrew Nacin 6:51 am on October 17, 2012 Permalink
    Tags:   

    Trac email issues are fixed 

    Unfortunately, the Trac mailing lists for WordPress Core and BuddyPress were missing many tickets and comments over the last few days. (From about October 15, 12pm ET to about October 17, 2am ET, an hour ago.)

    I OK’d a change to the Trac configs, but forgot about the restrictive mailman rules designed to block spam on these read-only lists. My bad.

    Many of us of course rely on these mailing lists, to the point where if it fails, we miss comments or entire tickets. To explain why you may have gotten some emails, but not all: You would have gotten it directly from Trac (rather than the mailing list) if you were already participating on a ticket.

    I’ve added support for ticket comments directly in the Trac timeline across all Trac instances on wordpress.org. Here are links to days with missing time periods:

    Note that the “From” email for these mailing lists is now noreply@wordpress.org. Rather than something@lists.automattic.com. You may need to adjust Gmail filters as appropriate (there hasn’t been a spam issue on these lists for some time; consider targeting list headers).

    Let me know if you have any lingering issues or questions.

     
  • Andrew Nacin 5:35 pm on October 10, 2012 Permalink
    Tags:   

    Please suggest items for today’s IRC dev chat. Today is the target date for Beta 2. Let’s figure out what we need to get done.

     
    • Marko Heijnen 6:16 pm on October 10, 2012 Permalink | Log in to Reply

      I was wondering if the plugins ‘Atom Publishing Protocol’ and ‘Link Manager’ also should have WordPress as an author. It does seem like a ‘core’ plugin

    • GrahamArmfield 8:24 am on October 11, 2012 Permalink | Log in to Reply

      Hi Andrew. I’ve seen a flurry of activity around some of the accessibility tickets that I and others raised during the summer, and I’ve seen some changes in the latest versions of the admin screens. This is great but I wondered how work was progressing on making the Theme Customizer fully keyboard operable?

      I’m guessing also that an accessible version of the Custom Menu builder is not being progressed for 3.5. Is that correct?

  • Andrew Nacin 5:47 pm on October 3, 2012 Permalink
    Tags:   

    Please suggest items for today’s IRC dev chat.

    I think the goal for today is:

    • Determine how 3.5 Beta 1 was received. Any major bugs? Any lingering issues we need decision points on? How do the support forums and Trac queues look?
    • Determine the goals for Beta 2, dropping next week. (After that, one beta per week until we transition to RCs.) Media needs a final push, and a few things still need to land. We need to start looking at closing out tasks/projects that are in trunk but need tweaks, testing, or changes to consider them done.
     
  • Andrew Nacin 7:45 am on September 27, 2012 Permalink
    Tags:   

    (Maintenance started around 8:18 AM UTC and finished around 9 AM.)

    Original post. Our main SVN server is undergoing maintenance early shortly. It should take less than an hour (once it starts). During that window, no WordPress.org Subversion repositories will respond. The exception is http://plugins.svn.wordpress.org, which is on a different server.

    The 3.5 Beta 1 and Twenty Twelve releases are delayed until after this is done, so see you all late Thursday morning.

     
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
shift + esc
cancel