Hello,
Since sql-parser is now another library we include, should we add ChangeLog entries for sql-parser issues that have been fixed in phpMyAdmin?
It seems to me this would be good, since sql-parser is closely tied to the functionality of phpMyAdmin (as opposed to, say, tcpdf where the user doesn't care as long as they can still press the PDF button and get a PDF file). However, it is a bit harder to follow which version of sql-parser is with which phpMyAdmin release, since they're not directly linked and we pull the most recent sql-parser 3.x when creating a release.
What's the consensus with the rest of the developers here?
Hi
Dne 25.2.2016 v 21:20 Isaac Bennetch napsal(a):
Hello,
Since sql-parser is now another library we include, should we add ChangeLog entries for sql-parser issues that have been fixed in phpMyAdmin?
It seems to me this would be good, since sql-parser is closely tied to the functionality of phpMyAdmin (as opposed to, say, tcpdf where the user doesn't care as long as they can still press the PDF button and get a PDF file). However, it is a bit harder to follow which version of sql-parser is with which phpMyAdmin release, since they're not directly linked and we pull the most recent sql-parser 3.x when creating a release.
What's the consensus with the rest of the developers here?
I think bug fixes should be mentioned on release and I believe that's what Dan does on every sql-parser update.