Original report by Jonas Bernoulli (Bitbucket: tarsius, GitHub: tarsius).
About two months ago Bitbucket announced that they would drop support for Mercurial by June 1, 2020.
This Emacs package is distributed on Melpa and we would like to ask you migrate the repository before Bitbucket deletes it.
Of course you have the option to stick with Mercurial (in which case you have to migrate to another forge) or you could stick with Bitbucket (in which case you have to convert to Git), but since Magit is getting quite a bit of praise and since you already have an account on Github, I recommend you switch to Git and Github.
If you migrate away from Bitbucket, then please make sure to link to the new location. If you keep the Mercurial repository until Bitbucket deletes it on June 1 2020, then you should do so in the README. Otherwise you can do so during the deletion of the repository (there is a field for that).
See our tracker issue for instructions on how to convert to Git. Spoiler: We have already done it for you.
Once you have migrated the repository, please comment on Melpa's tracker issue. If you feel like it, you could also update the Melpa recipe of your package yourself. If you do, then mention me (@tarsius) in the pull-request to make sure that I see it.
Thanks!
Original report by Jonas Bernoulli (Bitbucket: tarsius, GitHub: tarsius).
About two months ago Bitbucket announced that they would drop support for Mercurial by June 1, 2020.
This Emacs package is distributed on Melpa and we would like to ask you migrate the repository before Bitbucket deletes it.
Of course you have the option to stick with Mercurial (in which case you have to migrate to another forge) or you could stick with Bitbucket (in which case you have to convert to Git), but since Magit is getting quite a bit of praise and since you already have an account on Github, I recommend you switch to Git and Github.
If you migrate away from Bitbucket, then please make sure to link to the new location. If you keep the Mercurial repository until Bitbucket deletes it on June 1 2020, then you should do so in the README. Otherwise you can do so during the deletion of the repository (there is a field for that).
See our tracker issue for instructions on how to convert to Git. Spoiler: We have already done it for you.
Once you have migrated the repository, please comment on Melpa's tracker issue. If you feel like it, you could also update the Melpa recipe of your package yourself. If you do, then mention me (@tarsius) in the pull-request to make sure that I see it.
Thanks!