Differences between revisions 16 and 17
⇤ ← Revision 16 as of 2020-10-13 13:24:59 →
Size: 4156
Editor: Pierre-YvesDavid
Comment:
← Revision 17 as of 2020-10-13 13:40:18 → ⇥
Size: 5009
Editor: RaphaelGomes
Comment:
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
|| Raphaël Gomès || UTC+1 || (./) || <!> * || (./) || (./) || (./) || (./) || (./) || * Same as Pierre-Yves ||
Line 73: Line 74:
=== Dropping Python 2 ===

When do we do it? Do we drop everything compat that is not 3.5.4+? Are we waiting on PyOxidizer?

=== State of Rust ===

- Discuss the current state of the project and what the features underway will become in a few months.
- Discuss merging or not merging rhg/chg/hg with the help of PyOxidizer

=== Mercurial layered architecture ===

Alphare: slowly refactoring Mercurial into a two-layer codebase is something I've been thinking about over the past few months since the Rust implementation has adopted this split of core + consumer from the get-go. This is not a call to change everything right now but more of a "what do you think about this as a general direction in the next few years?".

Note:

This page is primarily intended for developers of Mercurial.

5.6 Sprint

Contents

  1. Date and location
    1. People Availability
  2. Attendance
  3. Possible Topics
    1. Tags
    2. Releases
    3. Shelve using archived phase
    4. Replication-friendly repository format
    5. Combined revlog
    6. More command "namespace"
    7. Google's --changeset-as-wdir feature
    8. Dropping Python 2
    9. State of Rust
    10. Mercurial layered architecture
  4. Sprint Notes

/!\ Subscribe to this page so you don't miss updates!

1. Date and location

This sprint will be held online. Perhaps the week of November 2 (right after the 5.6 release)? Let's see how that works for people and we can change otherwise.

To allow people from many different time zones to participate, we'll probably have to choose topics first and then choose a time zone for each topic that best fits the participants interested in that topic.

1.1. People Availability

Name

Time Zone

Nov 2

Nov 3

Nov 4

Nov 5

Nov 6

Nov 7

Nov 8

Notes

Martin von Zweigbergk

US West Coast

(./)

(./)

(./)

(./)

(./)

(./)

(./)

Jeff Sipek

US East Coast

(./)

(./)

(./)

(./)

(./)

(./)

(./)

Augie Fackler

US East Coast

(./)

(./)

(./) *

(./)

(./) *

(./)

* Monday and Wednesday I'm unlikely to be able to focus until around 1400 America/New_York. Other days all easy.

Jörg Sonnenberger

Central Europe

(./) *

(./)

(./)

(./)

(./)

(./)

Matt Harbison

US East Coast

(./)

(./)

(./)

(./)

(./)

(./)

(./)

Rodrigo Damazio Bovendorp

US West Coast

(./)

{X}

(./)

(./)

(./)

(./)

(./)

Danny Hooper

US West Coast

(./)

(./)

(./)

(./)

(./)

(./)

(./)

Manuel Jacob

Central Europe

(./)

(./)

(./)

(./)

(./)

(./)

(./)

Pierre-Yves David

UTC+1

(./)

<!>*

(./)

(./)

(./)

(./)

(./)

* Tuesday is a meeting minefield already. But still a lot of time available.

Raphaël Gomès

UTC+1

(./)

<!> *

(./)

(./)

(./)

(./)

(./)

* Same as Pierre-Yves

2. Attendance

<!> fill me when dates have been picked

3. Possible Topics

Important things we want to discuss: (add your own)

3.1. Tags

Multiple large users have their own overwrite of Mercurial tag system. It is worth reviewing what and why they do it and maybe make plan to improve the situation accordingly.

3.2. Releases

Right now durin42 is doing all the releases, and has some help doing release notes. It'd be nice to have others start rolling releases. Is anyone interested? Can we automate this more?

3.3. Shelve using archived phase

What needs to be done to get this to replace current shelve?

3.4. Replication-friendly repository format

durin42 is interested in (and has a handwave of a design for) a storage layer that would be replication-friendly. Basically, "how could we restructure repo storage so that it would be safe to put in {Dropbox,CIFS,etc}"?

3.5. Combined revlog

(added by Pierre-YvesDavid, this is orthogonal to the previous format proposal)

Storing multiple files history into the same filelog could help our disk footsprint and performance.

It "just" mean to add an extra "key" to address content, logic to find the right filelog and some logic adjustement through the code.

I have no hard plan yet, but I wanted to discuss that more broadly.

3.6. More command "namespace"

Right now we have the normal namespace and the "debug" namespace. It would be useful to have a couple more explicit namespace with their own guarantee. For example one dedicated to maintenance command (debugupdatecache, debugrebuildstate, debugupgraderepo, etc…) and one for other tooling (eg: debugcompletion)

3.7. Google's --changeset-as-wdir feature

Multiple contributors from google are trying to have various existing commands being able to consider a revision in place of the working copy. This is an interesting and powerful idea that is worth discussing in greater length. See plan page.

3.8. Dropping Python 2

When do we do it? Do we drop everything compat that is not 3.5.4+? Are we waiting on PyOxidizer?

3.9. State of Rust

- Discuss the current state of the project and what the features underway will become in a few months. - Discuss merging or not merging rhg/chg/hg with the help of PyOxidizer

3.10. Mercurial layered architecture

Alphare: slowly refactoring Mercurial into a two-layer codebase is something I've been thinking about over the past few months since the Rust implementation has adopted this split of core + consumer from the get-go. This is not a call to change everything right now but more of a "what do you think about this as a general direction in the next few years?".

4. Sprint Notes

General overview (drop the anti spam part): https://public.etherpad-mozilla.org/p/sprint-hg5.6-NOSPAMREMOVETHATLASTPAST

The table below is an attempt to gather written summary of discussion

Session theme

notes/result

People who know what happened

CategoryMeetings

5.6Sprint (last edited 2020-11-13 19:14:25 by Mathiasdm)