Diff for "1.7sprint"

1.7 Developer Sprint

1. About

This is going to be a long weekend of in-depth Mercurial discussion, design, and coding. It is open to all significant Mercurial contributors. See 1.5sprint for history.

2. Possible Agenda

• Lightweight copies, parent deltas, shallow clones
• Wire protocol improvements
• Performance improvements
• Usability
• Stable inotify, passing some kind of python run-tests.py --inotify *
• Web UI improvements/overhaul
• Safe, easy to use history editing/changeset staging system
• Improving bookmarks integration
• Subrepositories
  • What is the roadmap for subrepos?

  • Should we use subrepos ourselves? The polib library is a candidate since we already include a snapshot of it.

• Dead heads: a way mark heads that should not be pushed or pulled: original email, patch queue

• Move extensions to core: progress (should be enabled by default), record (for hg commit -i), transplant

• Eradicate test failures in our continuous integration server -- spurious failures makes the apycot build server less than ideal today
• Extract and publish API documentation from docstrings with Sphinx

3. Costs

We will fund hotel for all attendees. Where possible, attendees should try to get their employers to cover travel. We refund personal travel costs based on available funds and contribution level.

4. Date and Time

The sprint will be in Chicago on October 8th-10th. This will allow us time to put some work started at the sprint into 1.7 before the code freeze on October 15th.

The Fairfield Inn hotel has been booked for three nights from October 7th to 10th -- checkin is Thursday, checkout is Sunday. You need to make other reservations if you arrive earlier or leave later.

5. Travel

Make sure you have your passports and visas figured out in advance. Plan to arrive the day before the sprint begins to be ready for a full day of workshop.

6. Attendees

Add your name and other details here if you're interested in attending.