Hi all,
There is now a wiki page explaining the new Heptapod contribution workflow.
https://www.mercurial-scm.org/wiki/Heptapod
The previous email contained the complete expected timeline, but I'll
repeat it here to make it extra obvious for this particular concern:
- contributions using this workflow will be possible starting May 16th
- contributions through Phabricator will be deprecated on the same day.
- contributions through Phabricator will not be possible starting June 1st.
We have a couple of things to polish and there (like updating the rest
of the wiki, etc.), but the base is pretty much ready so I though I'd
send the email sooner rather than later.
Raphaël
On 5/2/22 21:38, Raphaël Gomès wrote:
Hello all,
It is time to set a flag day for our migration to Heptapod as a review
tool.
We are currently making very good progress with the team at OSUOSL who
will - unless a disaster occurs - provide us with infrastructure and
help with the migration, the details of which are being ironed out
right now. This is the most confident I have ever been about a smooth
transition, thanks again to the OSUOSL¹.
Mercurial 6.1.3 should be released on or right after the 1st of June.
Phabricator will need to be set to read-only mode before the VM goes
out of support to give us a window between it being deprecated and it
going out of service entirely.
I think a month is the best we can do for such a migration. More
clearly (all dates are best-effort and may differ by a couple of days):
- Patches will be accepted to Phabricator until May 30th
- Patches will be accepted to Heptapod starting May 16th (a separate
email will explain this)
- hg-committed will become deprecated in favor of the Heptapod repo on
May 16th
- Phabricator will be set to read-only on June 1st
- We will run the scripts that save Phabricator as an archive (I have
developed them already and have done a successful run)
- The archive will be made public for people to look at and check what
we've missed before it's too late
- Phabricator will be replaced by its archive on July 1st
- hg-committed will simply redirect to hg at some point after the
migration
This will be going on while we make the infrastructure migration
happen and answer to our other obligations whether work-related or
personal, so please bear with us if anything is sub-optimal.
I am confident that Mercurial as a project will be a lot healthier in
terms of tooling within the next few months, and while not everything
will be perfect, we are taking multiple good steps forward IMO.
Feedback is appreciated, as always.
Raphaël
[1] https://osuosl.org
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
