<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PDF/A-1a generated is not compliant" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113448#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PDF/A-1a generated is not compliant" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113448">bug 113448</a> from <a class="email" href="mailto:serval2412@yahoo.fr" title="Julien Nabet <serval2412@yahoo.fr>"> Julien Nabet</a> <pre>(In reply to Cor Nouws from <a href="show_bug.cgi?id=113448#c11">comment #11</a>) > jenkins says OK, and you see it works, so why not push? > Our users & QA will discover if it breaks anything. Because of the Miklos' comments in gerrit patch. Jenkins says it's ok for the build and the tests associated but I don't think there are hundreds of pdfs tested. This patch makes this case ok but, since neither Miklos nor I know pdf enough, it could trigger lots of regressions. I wouldn't like to potentially provide a lot of extra work to QA, there's already enough when you see the number of existing cases just to fix this bugtracker. The next step could be to propose the patch on dev mailing list but since I guessed more this patch than really understood how the whole thing worked, I suppose I'd be bashed :-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>