The second evaluation of GSoC was conducted between 24-28th July, and I have passed the evaluation.As we near the time for the final evaluation, I wish to improve upon the extension to make it ready to use for the next Mercurial version release.
After iterating several times over the patches based on similarity check, the code has been finally added to the default branch. With this addition, we have the basic ability of de-duplication in the releasenotes extension. The next thing is to add tests for checking commit messages for admonitions. Now, the issue here is that some changes would be worth adding to notes while the others wouldn’t. So we can’t put a compulsion on having admonitions in each and every release notes. So for now, we only check that if there exists an admonition in the commit message, then check if it is a valid one or not. This is done by checking if it exists in the list of default and custom admonitions.
Initially, I added this test to the contrib/check-commit where all the logic to check a commit in Mercurial is usually added. But Yuya has suggested that I should rather have it as a sub-command (like an additional flag –check) along with releasenotes, since the task depends on a couple of mercurial sub-modules.