[RFC] Storing changeset ID for sync in releasenotes and new features

[Rishabh Madan]

Hello everyone!

I have been working on the releasenotes extension as part of GSoC project.
As I am reaching towards the end of the final evaluation deadline, I want
to finish with a couple of things related to this extension.

I have previously discussed about the --sync flag for releasenotes
extension on IRC. It basically updates the notes file starting from the
last synced changeset to the latest one ('.'). But for this purpose I need
some method to store the last synced changeset that can be used later for
the next sync. Upon some discussion, we have two methods:
(1) Store the key, value pair of (branch, lastsyncedchangeset) in a file
separately and read from it (also update it).
(2) Store it in an encrypted form at the start of the notes file.

The (2) option has a downside that the notes will be copy-edited at some
point of time so it is unsafe to have this in such a file.
I would like to know your opinion about it and if there are any other
options to accomplish this task.

Also, I'm looking out for new features that can be added to this extension.
So any suggestions are welcome.

Thanks!
-- 
Rishabh Madan
Second Year Undergraduate student
Indian Institute of Technology, Kharagpur
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20170818/495e61cd/attachment.html>