Tag Archives: trac

Andrew Nacin 6:58 pm on September 10, 2012
Tags: trac   

Trac updates and a design refresh

Every few months we make a few improvements to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. Given how many hours so many of us spend on there, even the smallest changes can make a big difference. Today, a few new changes were deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors..

The first thing you’ll notice is a design refresh, from @helenyhou and @ocean90. It cools down the colors a bit and places more of our own mark on it (more WP-like, less Trac-y). They also added responsiveness for mobile devices, and made some adjustments to improve readability. See #18211. If you notice any bugs or quirks, please leave a comment there.

From @iammattthomas, the WordPress logo is now HiDPI.

If you’re a bug gardenerBug Gardener A contributor who has been given advanced privileges in Trac. (i.e. you can change milestones, etc.), you can now change the resolution of a closed ticketticket Created for both bug reports and feature development on the bug tracker.. This should make @sergeybiryukov happy — no more re-open to re-close.

Over the last few weeks I’ve given more than a dozen people bug gardener status. We’d like to empower the people we know and trust to make decisions, while making Trac simpler for others.

For those who aren’t bug gardenersBug Gardener A contributor who has been given advanced privileges in Trac., we’re trying to make it as easy and streamlined as possible for you to create and contribute to tickets. @bpetty has been studying our workflow and recommending changes. One of those is we’ve hidden the ability to change ownership of a ticket (accept/assign/reviewing). A big issue with ownership is it sometimes discourages others from contributing. I hope this change can free us up to using that field for tracking responsibility and accountability.

Non-gardeners can also no longer label tickets a “task”. Also, once the Version field is set, a user can’t update the field to a newer version, only an older one. (As @sergeybiryukov says, “version number indicates when the 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. was initially introduced/reported.” It’s the earliest known affected version for a bug, or the earliest applicable version 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..)

And finally, if you add the “has-patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.” keyword to a ticket, “needs-patch” will automatically be removed, and vice versa. (It’s the little things.)

I hope you enjoy this round of changes. If you have any further suggestions, please share in the comments.

Bonus. A few weeks ago, we added a ticket graph, inspired by jQuery and using their plugin as a base. I hope to add some more functionality to this in the future. For now, a few of us are using it to study trends and come up with some new ideas for how we can best maintain the ticket queues.

#trac

Andrew Nacin 12:33 am on November 16, 2011
Tags: trac   

I cleared out all tickets in Awaiting Review…

I cleared out all tickets in Awaiting Review with a reported version of 3.3. They would normally show up at the top of report 40.

If anyone wants to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. the next group — “Defects Awaiting Review, reported against no version” (59 tickets) — here’s some ways to triage a ticketticket Created for both bug reports and feature development on the bug tracker.:
— If it’s 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. or 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., change the ticket type.
— If it’s 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. that effects a previously released version of WordPress, then change the version field.
— If there isn’t enough information in the ticket, ask the reporter for more information and add the “reporter-feedback” keyword.

The main goal here is to identify regressions from 3.2 to 3.3, i.e., things that broke during this development cycle. We typically do a sweep each release not long before RC1, to make sure we didn’t miss a bad bug that was already reported.

#trac

Andrew Nacin 12:09 am on July 21, 2011
Tags: trac   

I’ve ported over all of the core Trac…

I’ve ported over all of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. modifications to the BuddyPress and bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. Tracs. In the process, core Trac has been given a fresh coat of paint, and the old Trac logo has been retired.

Also in the process, I’ve fixed a few bugs:

  • Bad link to the Security FAQ, #17479
  • Ticketticket Created for both bug reports and feature development on the bug tracker. fields are too wide in Firefox, #16582
  • Keywords cannot be removed on some browsers (well, Android) thanks to missing href attribute

Thanks JJJ, MT, and Barry for their assistance.

#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