Size: 5523
Comment:
|
Size: 6151
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 106: | Line 106: |
=== Is `hg evolve --all` discouraged? Should it be? :) (Kyle Lippincott) === Frequently users at Google just run `hg evolve --all` instead of more focused evolves, and dislike that after `hg evolve --all` they are on the tip-most revision instead of the revision they started on (or potentially the successor of that revision). I'd like to discuss changing this movement behavior (via a flag and/or config option). The subject is based on my (possibly flawed) recollection that the movement is happening because `hg evolve --all; hg co .^^; hg amend; hg evolve --all; hg co .^; hg amend; ...` is really not recommended. |
Note:
This page is primarily intended for developers of Mercurial.
4.0 Sprint
Contents
- Date and location
- Attendance
- Travel tips
- Sponsors
- Meals
-
Possible Topics
- Project infrastructure (Kevin Bullock)
- Refactoring changegroup API (Gregory Szorc, Pierre-Yves David)
- Topics (Sean Farley, Erik van Zijst, anyone else)
- MergeDriver internals (Siddharth Agarwal, ...)
- StreamClone and Batch wireproto enhancements (durin42, indygreg)
- Is `hg evolve --all` discouraged? Should it be? :) (Kyle Lippincott)
- Your topic here! (Your Name)
- Sprint Notes
Subscribe to this page so you don't miss updates!
1. Date and location
The sprint will be held at the Mozilla office in Paris, Oct 7-9. More info about the office can be found at https://wiki.mozilla.org/Paris.
Location point of contact: Gregory Szorc (indygreg) - gps@mozilla.com
If you need a formal invitation for visa purpose, contact the person above.
2. Attendance
Everyone is welcome from core developer to aspiring contributor. Attending a Mercurial sprint is usually a good way to kickstart your contributions and you'll get a large amount of help available for 3 days.
Name |
Coming from |
Need funding |
Hotel |
In Town Dates |
Notes |
Aaron Kushner |
SF |
no |
Ibis Paris Grands Boulevards Opera |
Oct 7-10 |
|
Augie Fackler |
PIT |
no |
The Chess Hotel |
Oct 6-10 |
|
Aurélien Campéas |
Paris |
no |
local |
Oct 7-9 |
|
Cotizo Sima |
London |
no |
TBD |
TBD |
|
Denis Laxalde |
France |
no |
TBD |
Oct 7-8 |
|
Durham Goode |
California |
no |
Westminster |
Oct 6-9 |
|
Erik van Zijst |
California |
No |
Best Western Hotel Ronceray Opera |
Oct 4-11 |
|
Gábor Stefanik |
Budapest |
no |
Best Western Anjou Opera |
Oct 6-10 |
|
Gregory Szorc |
SF |
no |
The Chess Hotel |
Oct 5-10 |
|
Jeremy Fitzhardinge |
SF |
no |
Ibis Paris Grands Boulevards Opera |
Oct 7-10 |
|
Katsunori Fujiwara |
Japan |
yes |
Best Western Diva Opera |
Oct 6-10 |
|
Kevin Bullock |
Minnesota |
yes |
Best Western Hotel Opera Drouot |
Oct 5-10 |
|
Kostia Balytskyi |
London |
no |
Westminster |
Oct 6-9 |
|
Kyle Lippincott |
California |
no |
Villathena |
Oct 3-11 |
|
Mads Kiilerich |
Denmark, Unity |
no |
Best Western Hotel Ronceray Opéra |
|
|
Mathias De Maré |
Belgium |
no |
Kyriad Paris Gare du Nord |
Oct 6-9 |
|
Philippe Pepiot |
France |
no |
TBD |
Oct 6-8/9 |
|
Pierre-Yves David |
Paris |
no |
local |
local |
|
Pulkit Goyal |
New Delhi |
yes |
TBD |
Oct 6-10 |
|
Remi Chaintron |
London |
no |
TBD |
TBD |
|
Rodrigo Damazio Bovendorp |
California |
no |
Best Western Hotel Ronceray Opera |
Oct 6-10 |
|
Ryan McElroy |
London |
No |
Westminster Hotel |
Oct 6-10 |
|
Sean Farley |
California |
No |
Best Western Hotel Ronceray Opera |
Oct 4-11 |
|
Siddharth Agarwal |
SF |
no |
Westminster Hotel |
Oct 6-9 |
|
Simon Farnsworth |
London |
No |
Westminster Hotel |
Oct 6-9 |
|
Wez Furlong |
California |
No |
Westminster Hotel |
Oct 6-9 |
|
Yuya Nishihara |
Japan |
maybe |
Richmond Opéra |
Oct 6-10 |
|
Piotr Listkiewicz |
Cracow |
yes |
TBD |
Oct 6-9 |
|
Jun Wu |
London |
no |
Westminster Hotel |
Oct 6-9 |
|
Mateusz Kwapich |
London |
no |
Westminster Hotel |
Oct 6-9 |
|
Stanislau Hlebik |
London |
no |
Westminster Hotel |
Oct 6-9 |
|
Martijn Pieters |
London |
no |
TBD |
Oct 6-9 |
|
3. Travel tips
If you need a smartphone to use while in Paris, http://www.insidr.paris/ is an option.
4. Sponsors
We need funds to pay flights and hotel for a few independent contributors.
Recent sprints sponsoring budgets were around $10,000. ( review this number)
Sponsoring Company:
Please offer some sponsoring
Sponsor point of contact: Please offer your service
5. Meals
Having Food delivered for Lunch is usually preferred as it help keeping the timing under control. Dinner is usually taken outside to help people cool off after a day of work.
(Don't forget vegetarian and vegan option)
Meal point of contact: Location not picked yet
Day |
Meal |
Details |
Organizer (when relevant) |
Friday |
Lunch |
|
|
Friday |
Diner |
|
|
Saturday |
Lunch |
|
|
Saturday |
Diner |
|
|
Sunday |
Lunch |
|
|
Sunday |
Diner |
|
|
6. Possible Topics
It worked well at the last sprint to devote some of the time to "unconference"-style sessions, proposed by attendees and scheduled into a grid of timeslots and rooms. Do we want to plan on that again? —KevinBullock
Important things we want to discuss:
6.1. Project infrastructure (Kevin Bullock)
I'll give a report on the current state of the project's infrastructure (server, buildbot, bugzilla, mailing lists, &c.), and walk people thru the config automation we've done via Ansible and Docker. Hoping to get some more people familiar with it so they can solve problems when they arise.
6.2. Refactoring changegroup API (Gregory Szorc, Pierre-Yves David)
See discussion at: https://www.mercurial-scm.org/pipermail/mercurial-devel/2016-August/086763.html
6.3. Topics (Sean Farley, Erik van Zijst, anyone else)
Flesh out topics: https://www.mercurial-scm.org/wiki/TopicPlan
6.4. MergeDriver internals (Siddharth Agarwal, ...)
Talk (~1h) about internals of MergeDriverPlan + whatever work we end up doing next.
6.5. StreamClone and Batch wireproto enhancements (durin42, indygreg)
Seem related. Streamable and reorderable batch.
6.6. Is `hg evolve --all` discouraged? Should it be? :) (Kyle Lippincott)
Frequently users at Google just run hg evolve --all instead of more focused evolves, and dislike that after hg evolve --all they are on the tip-most revision instead of the revision they started on (or potentially the successor of that revision). I'd like to discuss changing this movement behavior (via a flag and/or config option). The subject is based on my (possibly flawed) recollection that the movement is happening because hg evolve --all; hg co .^^; hg amend; hg evolve --all; hg co .^; hg amend; ... is really not recommended.
6.7. Your topic here! (Your Name)
Add your own topics here.
7. Sprint Notes
General overview (drop the anti spam part): https://public.etherpad-mozilla.org/p/sprint-hg4.0-NOSPAMREMOVETHATLASTPAST
The table below is an attempt to gather written summary of discussions
Session theme |
notes/result |
People who know what happen |