Community
Participate
Working Groups
Bugzilla 3.5.3 has the following change * comments for attachments changed from Created an attachment (id=????) to Created attachment ???? This breaks SaxMultiBugReportContentHandler.parseAttachment so Creator and created are no longer filled.
We can use the child tags from <attachment> for the created (Tag <date) and Creator (Tag <attacher>) information. So there is no need for grep the comment text. We then cane use tag <delta_ts> for last mod date. This works with older Bugzilla versions to. Thoughts?
When is 3.6 scheduled to be released?
(In reply to comment #1) > We can use the child tags from <attachment> for the created (Tag <date) and > Creator (Tag <attacher>) information. > > So there is no need for grep the comment text. > > We then cane use tag <delta_ts> for last mod date. > > This works with older Bugzilla versions to. > > Thoughts? Sound right Frank. (In reply to comment #2) > When is 3.6 scheduled to be released? July 13
Should this get scheduled for 3.4? Seems important that we would have support for Bugzilla 3.6 as part of Helios.
Created attachment 159063 [details] commited patch CreationDate and Autor for Attachments can now parsed in new and old format.
Created attachment 159064 [details] mylyn/context/zip
Frank, did you manage to setup a test repository for 3.6?
(In reply to comment #7) > Frank, did you manage to setup a test repository for 3.6? Yes the repository is available but I need to finis the setup (add users,..) and config the XMLRPC components
Just copy (dump/restore) a databases from Bugzilla 3.4 and let checksetup do the rest.
Created attachment 166121 [details] commited patch Now we have an bugs36 test repo at http://mylyn.eclipse.org/bugs36/ I have create the new file clean_bugs_3_6_with2bugs.sql that you can load to restore the database. All test pass with no error.
Created attachment 166122 [details] mylyn/context/zip
Created attachment 166129 [details] patch add test for verify that XMLRPC is installed. This use http://mylyn.eclipse.org/bugs36noxmlrpc/ which use the same database as http://mylyn.eclipse.org/bugs36/ .
Created attachment 166130 [details] mylyn/context/zip
Great stuff, Frank! Here are a two minor suggestions: * Rename BugzillaXMLRPCTest to BugzillaXmlRpcTest to make it consistent with the project naming conventions. * Consider creating fixtures for the added repositories, e.g.: public static BugzillaFixture BUGS_3_6_XML_RPC_DISABLED = new BugzillaFixture(BugzillaTestConstants.TEST_BUGZILLA_36_URL + "noxmlrpc", // "3.6", "XML-RPC disabled"); public static BugzillaFixture BUGS_3_6_CUSTOM_WF = new BugzillaFixture(BugzillaTestConstants.TEST_BUGZILLA_36_URL + "customwf", // "3.6", "Custom Workflow"); We probably don't need to run all tests against the new repository, yet. The ones that invoke functionality related to XML-RPC or workflows should be sufficient.
Created attachment 167561 [details] patch now we have the following new repositories * bugs36noxmlrpc * bugs36customWF in place.
Created attachment 167562 [details] mylyn/context/zip
Created attachment 168437 [details] corrections see comment#14 here are the 3.6 specific fixtures BUGS_3_6_CUSTOM_WF, BUGS_3_6_NO_XMLRPC, BUGS_3_6_CUSTOM_WF_AND_STATUS and the following URL's http://mylyn.eclipse.org/bugs36-custom-wf http://mylyn.eclipse.org/bugs36-custom-wf-and-status http://mylyn.eclipse.org/bugs36-xml-rpc-disabled
Created attachment 168438 [details] mylyn/context/zip
What's left to do here?
(In reply to comment #19) > What's left to do here? I think we are done.