Tagged: trac Toggle Comment Threads | Keyboard Shortcuts

  • Eric 8:25 pm on November 29, 2012 Permalink
    Tags: branches, , trac   

    Since the in-app-sounds branch has been merged to trunk I’ve deleted it. While I was at it, in the name of tidying up a bit, I’ve removed a few other branches that were either empty or obsolete:

    I thought there might be something we might want to come back to in the flurry and hybrid branches so I’ve left them alone. I’m not sure what the sideswipe branch was for so I left it as well.

    I wanted to remove the numbered version branches since we have tags for all our releases, but it looks like the revisions don’t match their counterparts under tags so I held off. Is there a reason to keep these?

    • Koke 11:18 am on November 30, 2012 Permalink | Reply

      sideswipe was swipe to moderate comments. It should be all merged. IMO version branches can go too, I don’t think we’re going to ever use those. And I think you can always recover them since the history isn’t actually deleted from the svn repo

      • Eric 3:59 pm on November 30, 2012 Permalink | Reply

        Cool. I’ll finish pruning the branches then.

  • Koke 4:06 pm on November 21, 2012 Permalink
    Tags: trac   

    Looking for trac workflow ideas. Since we’re moving to a feature based development, how should we manage tickets and milestones?

    Current problems:

    • 3.3 milestone has a lot of tickets related to notifications and visual editor
    • Trac has no bulk ticket management, so it’s a pain to move them one by one every time a feature is pushed back
    • Once a version is released, it’s nice to have every ticket fixed in the right milestone as reference for changes in that version

    In summary, considering that 3.3 is going to be Sounds + bugfixes, I’m having a hard time figuring out what’s important by looking at http://ios.trac.wordpress.org/query?status=assigned&status=new&status=accepted&status=reopened&group=status&milestone=3.3

    How do we manage this better for future releases/features?

    • Daniel Bachhuber 6:33 am on November 22, 2012 Permalink | Reply

      Trac has no bulk ticket management, so it’s a pain to move them one by one every time a feature is pushed back

      There’s a bulk ticket management plugin you can install. We have it for VIP Review Trac. @nbachiyski knows more.

    • Koke 12:27 pm on November 22, 2012 Permalink | Reply

      Until we get bulk management, I got this user style: https://gist.github.com/4130919

    • Koke 2:37 pm on November 22, 2012 Permalink | Reply

      I’m thinking of replacing the priorities list with this:

      • Security
      • Crash
      • Major: bugs that can cause data loss/corruption
      • Minor: bugs that generate confusion
      • Wishlist: everything else.

      Not sure about what kind of ‘defects’ would go into wishlist, but it’d be the priority for enhancement tickets.


      • Isaac Keyet 6:59 am on November 26, 2012 Permalink | Reply

        Not opposed to doing these, but we should change them across all the mobile projects if we do. It would probably make more sense to keep calling the lowest priority items “trivial” if we’re keeping “major” and “minor” though – but it’s just wording. Doesn’t matter all that much.

      • Brad 3:28 pm on November 27, 2012 Permalink | Reply

        I think there should still be a “blocker for release” priority. Then we should make sure all blocker priority items are closed before a release.

    • Koke 3:19 pm on November 22, 2012 Permalink | Reply

      Some new reports after the 3.3 milestone cleanup:

      • {16} Next Release: now uses the ‘Next Release’ milestone. Not so useful for planning, but still there
      • {18} Features in development: tickets assigned to components ‘Notifications’ and ‘Visual Editor’. Should be updated for future features
      • {19} Open defects: list of all defects grouped by priority, showing age, last time updated, and keywords
  • Isaac Keyet 3:14 am on October 16, 2012 Permalink
    Tags: , trac,   

    Headsup: changed the “newui-3.1” Component to now be called “User Interface” since there’s a need to tag tickets as relating to the overall UI and/or graphics only.

    Tickets previously tagged with “newui-3.1” should now be tagged “User Interface”. Example: http://ios.trac.wordpress.org/ticket/1458

  • Koke 5:37 pm on March 5, 2012 Permalink
    Tags: 2.10, trac   

    I created the Next Release report on trac, priorities are:

    • Blocker: major features for the release
    • Critical: anything that worked before adding new features and it’s broken now
    • Major: generic bugs
    • Minor, trivial: enhancements that would be nice to include in the release if there’s time

    Not everything is in the right priority yet, but I think it’s a good way to sort priorities

    • Judy 1:11 pm on March 10, 2012 Permalink | Reply

      Im a PM who teaches web deign and dev, and has gotten into iOS. I would like to get involved. This would be my very first opensource participation, and if there is a proper protocol – I hope I havent just violated it by just replying to this post. If anyone can spare a little time to write me and point me in the right direction, I hope to make it up to you in contributions.

    • Usain 2:57 pm on April 1, 2012 Permalink | Reply

      Please add a feature to set a featured image, I miss that feature so hard and I know I’m not the only one.
      Keep up the good work!

      • Jorge Bernal 12:16 pm on April 2, 2012 Permalink | Reply

        Support for featured images has been added recently to the API for WordPress 3.4, it wasn’t possible until now. We’re working on bringing that to a next version of WordPress for iOS

  • Koke 4:25 pm on November 4, 2011 Permalink
    Tags: , , trac, wpios-3.0   

    I just emptied the 3.0 milestone on trac so we can start fresh.

    I’ll start working on the roadmap next week, and everything should have it’s own ticket so we can easily keep track of the changes and progress.

  • Koke 1:09 am on March 30, 2011 Permalink
    Tags: trac   

    I just did some trac housekeeping, closing 16 tickets (most of them fixed by 2.7), and organizing milestones and priorities.

    Sorry if you got a ton of emails because of that 😦

  • Chris Boyd 8:25 pm on September 11, 2010 Permalink
    Tags: , , trac   

    Bug reports – Anyone on the Beta Team having trouble submitting tickets in Trac? If so, you can just leave a report here as a comment.

    • Darnell Clayton 11:38 pm on September 11, 2010 Permalink | Reply

      Heh! Is our trac login tied to our forum login? If not I don’t remember receiving an ID!

      Anyways, I did find a lot of bugs ranging from crashes whenever you upload a video to a WP.org site as well as the inability to scroll down to view more content after you write (scroll bar error perhaps?).

      Also whenever I try to change the post from local draft to publish it crashes too. Anything else you need info on? 🙂

      • Chris Boyd 1:46 am on September 12, 2010 Permalink | Reply

        Yep – Trac login is tied to your forum login. I just tried to reproduce the inability to scroll issue and couldn’t do it. Were you on Posts or Pages?

      • Chris Boyd 1:53 am on September 12, 2010 Permalink | Reply

        Also, try adding this line to your root .htaccess file:

        php_value memory_limit 64M
    • Chris Boyd 1:35 am on September 12, 2010 Permalink | Reply

      Darnell – How long was the video you uploaded? There’s some changes you may need to make to your .htaccess file on your WPorg site to get it to work.

      Definitely need to talk more about the crashes when it changes from Local Draft to Publish. Could you tell me any more?

    • sutherlandboswell 2:56 am on September 12, 2010 Permalink | Reply

      Can’t log into the forum or Trac…

      Anyways, the issue I’ve already noticed is image ratios on the iPad. You can see the obviously stretched image at http://suthdevtest.wordpress.com/

      Another thing is that after tapping on an image in the media tab to view it full screen, there’s no back button… it took me a moment to figure out the delete button did the equivalent.

      When adding an image to a page, there’s no Save button until I modify the text, which people might think means it’s already saved or just not know how to save. I don’t have this problem when adding an image to a regular post.

      And a couple other little things…

      Lots of crashes after dealing with media.

      It seems like you’re aware of this, but preview isn’t working for me. Using a WordPress.com blog with the TwentyTen theme. No message, just a blank page when I choose preview.

      Keep up the good work!

    • nazaroth 9:43 am on September 12, 2010 Permalink | Reply

      One thing I have noticed. I just loaded up my blog, I know there is an article waiting to be published, but I don’t see it. The list of articles spans ALL articles now with no press to load more button, and no pending articles.

    • nazaroth 12:55 pm on September 12, 2010 Permalink | Reply

      Ok please ignore my last post :/

      I do have another bug though, when writing an article, when the text gets to the bottom of the window, it will keep going but I am no longer able to see what I am writing and cannot scroll down to see.

    • nazaroth 1:18 pm on September 12, 2010 Permalink | Reply

      Also after writing some text in a new article, if I then try to add some media, the “+” button is covered by the wordpress logo that shows auto saves, so I am unable to press the “+” button.

    • Darnell Clayton 1:51 am on September 13, 2010 Permalink | Reply

      Odd. I thought I’d subscribed to this thread?! I’ll check my spam box (sorry for the belated response).

      I’ll see about editing my .htcacess Chris, although I’ll be switching hosts in s month as my current one is slowing down.

      As far as posting goes, video uploads (regardless of size crash, and I am unable to scroll down within the app.

      I’ll see if I can reproduce these upon a WP.com site.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc