|Re: [wtp-dev] XSL Tools Release Plan page|
The way the queries work, they automatically reflect what happens as the appropriate target milestones are set. I can add the plan key word if that helps, but an item is planned in wst.xsl if it has the target milestone set, and is in Assigned, New, or ReOpened status. The queries only focus one milestone out. So are updated just before the end of one milestone and the beginning of the next.
In many ways, they are implementing many of the Best Practices, proposed by the Architecture Council. There are several groups include platform-ui that are starting to implement this way of working with bugzilla and managing the bug backlog.
Anyways, that is the reason for there being "no true owner" assigned to a particular bug. It allows anybody that has the time to work on the bug. Plus it helps to eliminate knowledge silos that can occur if certain people are only responsible for certain parts of the system.
Dave Nitin Dahyabhai wrote:
David Carver wrote:Just a note that I've updated the wst.xsl tools release plan with the list of bugs/enhancements on what has been planned/completed for WTP 3.2 so far.As mentioned in Raghu's earlier note (7/16), we're using the standard project plan format that draws items directly from Bugzilla. http://www.eclipse.org/projects/project-plan.php?projectid=webtools.sourceediting has pointed to our 3.2 queries for a while now, and a few items have already been marked and even completed. It is organized according to the same broad themes as before and is in keeping with the overall WTP plan document; simply mark bugs as plan items according to the instructions written within each theme. Not all bugs belong on the plan, though, just the bigger items (meta-bugs/umbrella items would for example, such as the W3C compliance bug itself). I'm sure Raghu is open to suggestions if you find the format lacking.Having more information in a wiki page is fine, particularly those useful Bugzilla queries, but you'll have to keep it up to date. And I would prefer it link to the WTP Source Editing plan.I only have one requirement in addition to Raghu's: a bug is not to appear as a Committed plan item (meaning it has a target milestone) unless it is assigned to someone other than the inbox. Over half of the M2 targeted XSL bugs showing up on the wiki page's query link have no real owner at this moment. I know we all want to accomplish a great deal with this release, but even those of us lucky enough to get to work on WTP full time need to keep in mind that there's more to what we do day-to-day than just churning out code. Our newsgroups could benefit from greater diligence from us all, and our builds are still breaking far too often.Regards, --- Nitin Dahyabhai Eclipse WTP Source Editing IBM Rational _______________________________________________ wtp-dev mailing list wtp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/wtp-dev
Back to the top