[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mylyn-docs-dev] Closing old bugs
|
Jeremie,
For bugs that truly are duplicates or fixed, closing them off is the right thing to do. Feel free to either mark them as a duplciate in Bugzilla, or close them as WORKSFORME indicating the version of Mylyn WikiText where it's known to work.
Thanks,
David
On Wed, Oct 31, 2012 at 2:18 PM, Jeremie Bresson
<dev@xxxxxxxx> wrote:
Hi everybody,
For a few days, I took time to analyze bugs of the Mylyn Docs project. I have focused in bugs related to the MediaWiki core (syntax support, parser, document-builder, ...).
I have identified some "old bugs". They are already fixed, or duplicate of fixed bugs. In my opinion they can be closed (sometime something can be done like adding a unit test, but it is not mandatory).
* [1] 331515 - Empty line in table cell make rest of text dropped in conversion from mediawiki to xsl-fo
* [2] 307448 - Case sensitivity of Eclipse Help
* [3] 349723 - Cannot create bold text inside <pre> element
* [4] 306112 - Problem with underscore character in image name
I wonder if my idea to add a comment on these bugs is the correct way to get them closed.
Does someone care about this? I think the persons who reported the bug in the first place, are no longer interested.
Could someone tell what the process is?
Thanks in advance for your answers,
Jeremie
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=331515
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=307448
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=349723
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=306112
_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev
--
David Green
VP of Engineering, Tasktop
Committer, Eclipse Mylyn
+1-778-588-6896 ext. 115