Define ticketing method for Opera and Safari support

[alfonso@…]

I'm trying to test if we can have a set of meta bugs (one for each browser) that can tell us the state of support for each browser.

I don't see the ability to have a Ticket depend on another one, maybe we can use then Keywords on each Ticket to know bugs affecting each browser?

Other ideas about how to track each browser and know for example what's missing in Opera or Safari to say that it's officially supported?

---

Depends on: #1, #2
Blocks: #3

[FredCK]

Being the work for compatibility something really important, and as it requires a lot of work, we could think about creating specific Milestones for it. We would usually use it for versions, but it would make sense in this case.

Unfortunately the Trac ticketing system doesn't support dependencies. This is something I've always missed on it. It seams they are working on it.

The "Keywords" have other usage, and the most important thing about dependencies is the possibility of quickly understand if the dependencies are opened or closed.

This behavior can be accomplished in the bodies of tickets descriptions or comments, by simply creating tickets links. So, as we all are able to make changes to tickets descriptions, we could add an horizontal line at the very end of this description and add two lines, one for "Depends on" and other for "Blocks", like the sample I'm adding in this ticket. What do you think?

[alfonso@…]

It isn't a perfect solution but at least it automatically links the bugs so we can try to use it.

One problem is that the bugs blocked by this one must be modified to update its "Depends on" list of bugs as new ones are added instead of that being automatically handled by the system (I really like the way Bugzilla handles this)

[FredCK]

Ok... I've created the Opera and Safari related milestones

And let's start now using the dependency system as we have defined. I have also documented it here document it here.