Tag Archives: trac

Andrew Nacin 9:39 pm on July 7, 2011
Tags: trac   

There’s a 3.3 milestone on Trac but please…

There’s a 3.3 milestone on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., but please, no tickets (except by committers) until we hold our scope session starting next week.

#trac

Andrew Nacin 11:46 am on June 21, 2011
Tags: trac,   

If anyone has time this week there are…

If anyone has time this week, there are about 100 tickets that need to be reviewed for potential 3.2 issues we missed. The first page of Report 40 lists “Defects Awaiting Review, reported against trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.” and “Defects Awaiting Review, reported against no version.”

Basically, we’re just looking for bugs to 3.2 features, and regressions. Many of these either need the version numbers dropped (or added) or converted to enhancements. If someone wants to do full triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me or someone in IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. and we’ll arrange milestone adjustments.

Update: Specifics on how to help.

  • The Version field is for the earliest known version that the ticketticket Created for both bug reports and feature development on the bug tracker. affects. For bugs, this would be the version to which it applies or was introduced. All the ones that say “3.2,” if they aren’t new bugs in 3.2, then they should be changed to 3.1 or, for extra credit, earlier.

  • If the ticket is pushing for an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature., rather than reporting a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority., then simply change the Type field to “enhancement.” (Rarely “feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged.,” never “task.”)

(Contributors who have participated on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. before will of course know to adjust keywords, perhaps even adjust milestones and what not. But these are two simple ways to help clean up this report.)

#trac, #triage

Andrew Nacin 5:56 pm on April 6, 2011
Tags: , trac   

The keywords fixed major and fixed…

The keywords “fixed-major” and “fixed-minor” can be used for tickets that span both a minor and major milestone. A ticketticket Created for both bug reports and feature development on the bug tracker. fixed in the major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. (and then usually re-opened for minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. consideration) will not show in reports 5 and 6. A ticket fixed in the minor release (and then usually needs more work for a major release) will not show in reports 3 and 4.

The ticket does need to remain open and set to the minor release milestone, so really it’s just a way for committers get it out of sight, out of mind when appropriate. Eventually a ticket tagged fixed-major will either be backported or not (and closed either way), and a ticket tagged fixed-minor should either be dealt with in a timely fashion, or split into two tickets.

#keywords, #trac

Andrew Nacin 6:29 pm on February 17, 2011
Tags: trac   

Second round of Trac changes went live earlier…

Second round of TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. changes went live earlier:

  • Reporters now automatically receive ticketticket Created for both bug reports and feature development on the bug tracker. updates via email.
  • Reporters are asked to add their email to Trac preferences if it isn’t there already. (Next step is pulling this directly from WP.org for all users, but it’ll take a bit of work.)
  • Reporters now see a notice when tickets are marked reporter-feedback. (This is embedded below.)
  • Tickets now need to be previewed before creation. This should cut down on formatting issues.
  • If you try to create a ticket in the Security component, you get a warning reminding you of the proper procedures for reporting suspected vulnerabilities.
  • The license note when uploading an attachment is more prominent and the upload button now explicitly says ‘Agree and Upload.’

#trac

Andrew Nacin 4:30 am on February 6, 2011
Tags: trac   

As 3.1 winds down and early 3.2 developm…

As 3.1 winds down and early 3.2 development is likely to start soon, I’m trying to make TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. a bit more usable, ranging from reports to the theme itself.

I’ve been tinkering with report 40, Tickets Awaiting Review. It now uses the type of ticketticket Created for both bug reports and feature development on the bug tracker., version it was reported against, and keywords, to create five groups of tickets:

  • Defects Awaiting Review, reported against trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. (or no version number specified)
  • Defects Awaiting Review, reported against latest branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".
  • Defects Awaiting Review (all other bugs)
  • Enhancements Awaiting Review (includes feature requests)
  • Reporter Feedback / Close (tickets marked for reporter-feedback or close, which overrides the other groups)

Each group is then sorted in descending order from when the ticket was last modified. Right now the first two groups are the same, but I’ll modify the report once 3.2 development starts.

Ideally, this will allow us to better track and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. incoming tickets. It also increases the significance of the ‘Version’ field (version it was reported against, but ideally earliest version to which the ticket applies) and removing reporter-feedback when feedback is provided.

I’ll be working on report 39 (Candidates for 3.2) soon. Suggestions welcome for improvements on both.

#trac

Andrew Nacin 11:20 am on January 21, 2011
Tags: trac   

General Trac usage note: Please don’t e…

General TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. usage note:

Please don’t edit your own comments beyond fixing typos or improper formatting. Many of us consume Trac through the mailing list, and adding to a comment or changing its meaning makes this much more difficult.

I don’t think it’s necessary to need to go through the process of installing a Trac pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to prevent comment editing. I’d just like to see edits be rare and trivial.

#trac

Andrew Nacin 5:54 pm on January 12, 2011
Tags: , trac   

Bulk action issues are somewhat outlined…

Bulk action issues are somewhat outlined in #16166 #16031 #16187. We’ve been able to group the issues into four problems.

Four problems needing solving:

Problem 1. Wontfixwontfix A resolution on the bug tracker (and generally common in software development) that indicates the ticket will not be addressed further. This may be used for acceptable edge cases (for bugs), or enhancements that have been rejected for core inclusion. for 3.1. Custom Bulk Actions don’t have action handlers. Even if they existed, developers would need to know that they need to call WP_List_Table::add_query_args() before wp_redirect. We need a way for this to be pluggable without burdening developers on redirecting (plus with their own query args).

Problem 2. Fixed. We need a sanity check for max pages. This is #16187. Basically, this needs to be applied to any other appropriate list tables. Most major ones (posts, comments, media) are handled though.

Problem 3. Bulk Actions reset the sorting and paging. This is fixed in #16166 (posts, terms, comments, media) but we need to apply this to the other list tables.

Problem 4. Post restriction filters — categories and dates, for example, but really anything added through restrict_manage_posts — are reset after a bulk action the same way sorting and paging are. This can be added into add_query_args().

The plan at the meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. here is to break on all of this, and revisit later.

#wptybee, #trac

Jen 6:33 pm on January 8, 2011
Tags: reporter-feedback, trac   

I know Trac is not always the most intui…

I know TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. is not always the most intuitive application. Having to set up email preferences in a profile, then add your name to the cc box on a ticketticket Created for both bug reports and feature development on the bug tracker. to get a notification when someone comments is not an optimal user experience. However, it’s what we have right now, and I’m thinking that maybe that non-intuitive flow is part of why there are over a hundred tickets that have been looked at and commented on, and are sitting around waiting for reporter feedback and/or steps to reproduce. In a few cases, the reporter-feedback tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) simply wasn’t removed when it should be, but most of them are still waiting for more info. If you have reported any bugs or requested any enhancements, please check the reporter-feedback queue to see if there’s anything waiting on more info from you. Thanks!

#reporter-feedback, #trac

Andrew Nacin 9:50 pm on December 17, 2010
Tags: i18n-change, string freeze, trac   

i18n-change: It’s that time again. This…

i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.-change: It’s that time again. This keyword must be used on any tickets that may or need to lead to a string change from now until the end of the cycle. We’ll use this to track when to call the string freeze, and then to track any times we need to break the freeze. (I will update the translators as necessary over at http://wppolyglots.wordpress.com.)

#i18n-change, #string-freeze, #trac

Samuel Wood (Otto) 9:17 pm on December 16, 2010
Tags: trac,   

Profiles now shows up-to-date info from …

Profiles now shows up-to-date info from the various tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. installs once again. It won’t be up-to-the-minute, but it will be updating on a somewhat regular basis.
Example: https://profiles.wordpress.org/users/nacin

#trac, #wporg