Hey everyone!  This is this update for this week. This blog describes basically how I started working on hg continue and got my first four patches approved.

What did I do this week?

This week I started my work on hg continue and sent the first patch regarding the logic for it [1]. Then subsequently I sent patches to add support for rebase[2] and unshelve[3] and also for graft and it was queued but as it wasn't too refined it had to be de-queued and sent the fix[4]. This leaves graft, tranplant and `histedit` to work on to complete hg continue plan.

What is coming up next?

This week I am planning to complete support for hg continue for graft, transplant and histedit and get that approved. Also, I will try to apply it move to evolve.
I also am still planning on getting my patches for hg abort for evolve merged as they still left to get reviews as community is busy with the release.

Did you get stuck anywhere?

I did get stuck when I started adding support for the functions but @Pulkit again helped me out of the situation. I was not sure how to pass on the opts for various commands when continuefunc is directly called . But the knowledge that opts are present in state file resolved it.

Greetings everyone!  This is this update for this week. This is all about how I
got hg abort finally added to Mercurial. I also sent PRs to evolve repository adding its support.

What did I do this week?

This week I improved hg abort further and finally got them accepted and merged. This marks the end of hg abort plan for Mercurial core repository.
It will now be shipped with Mercurial version 5.1. It is still marked EXPERIMENTAL though as there is still a little doubt regarding its perfectness.
Also, my patch for bug code 6160 was finally merged. Completing integration with the core I moved to  Mercurial's evolve repository and added support for hg abort for hg evolve --abort and hg pick --abort [1][2][3]. These patches are still under review.
I also started my work on hg continue and was able to develop a logic for it and also apply it for histedit.

What is coming up next?

This week I am planning to start sending patches on hg continue on Phabricator. Also I will try to apply it for the remaining commands in core and then move to evolve.
I also plan on getting my patches for hg abort for evolve merged.

Did you get stuck anywhere?

I did get stuck a little when working with evolve repository but @av6 and @marmoute covered most of them for me. Besides that I wasn't stuck in something that was major.

Hello people!  This is this weeks update. This week was spent mostly in the review of hg abort. It has now come up to be much refined and acceptable than it initially was.

What did I do this week?

This week I spent most of the time improving hg abort patches according to the suggestions of @Pulkit [1] [2] [3] [4] [5] [6] [7]. As the new release nears I was asked to mark it EXPERIMENTAL for now so that the related bugs can be dealt with before it is finally shipped with Mercurial.
I also worked on bug code 6160 [8]. Since it was very much related to the field I was working on so I was asked to fix it and I created a patch for that [9].

What is coming up next?

This week I am planning to start my work on hg continue and start sending the patches for that. I will also try to get hg abort and my patch on issue 6160 committed this week.

Did you get stuck anywhere?

I did not get stuck with anything major this week. Small minor doubts did arise but the community and my mentor @Pulkit helped a lot.

Hey everyone !  This is the update of what I did this week. This week I got my API and its extended cases committed. Also, I completed the implementation of hg abort and pushed the patches for review.

What did I do this week?

This week as stated previous blog I completed the implementation for hg abort and included shelve and merge in the plan. Also, I refined my patches and send them to Phabricator in a well-divided format.
In this period I also got my state detection API committed to the Mercurial repo. It's extended cases suggest by @martinvonz were dealt with and it was my patches were finally merged. I also updated the release notes regarding that. This marks an official end to the first sub-task that was the task of the unification of state detection APIs.

What is coming up next?

The coming week I am planning to get all of the patches for hg abort approved and update the patches according to the reviews. There might be a lot of new features that might be needed to be added to that as hg abort is still in its underdeveloped stage.
I will also work parallelly on hg continue and see if I can prototype it.

Did you get stuck anywhere?

I faced some problem when I was trying to include merge in the hg abort plan. Though it took some time, I was able to figure out the workflow and make an appropriate patch for it.
 

Hey everyone!!  This is the update for week 4 and hence the last week before the first evaluation. This week I mainly extended the state detection API to more cases which were not part of the plan but an essential for Mercurial. I also came up with the first implementation of hg abort. 

What did I do this week?

As stated in the previous blog I got my PRs regarding the first sub-task accepted.[1][2][3][4] @martinvonz suggested some extended cases for the API and I was interested to take that up and add those features. Also, I updated the release notes about the new API. 
For hg abort, I sent the first prototype for it which included the algorithm for hg abort, the extension of state detection API to register abort functions and inclusion of graft, rebase and histedit into the plan. This leaves me with two remaining operations merge and shelve. I was able to write a prototype for shelve but since it was buggy I did not send it as a PR. I got my patch reviewed by @Pulkit on Bitbucket [5]. He suggested me some changes I will send the patch directly to Phabricator.
   
What is coming up next?

The coming week I am planning to get all of the patches for extended API approved and will send the complete hg abort patch to be reviewed. The work that is still left is cleaning up the patch and inclusion of shelve and abort as part of abort plan. 
Towards the end of this week if time permits I would like to start with hg continue. 

Did you get stuck anywhere?

During the start of hg abort I did get stuck with what actually will the algorithm for it look like. Though I had a visualisation but was not quite clear with it. I discussed this with @Pulkit got my doubts cleared and went ahead with my work.