0.3.0 release planning

[pnorman]

The plan for 0.3.0 is to include the single-element and multi-element get calls

Targeted for 0.3.0 release

• /node/# tested
• /way/# tested
• /relation/# tested
• /nodes?nodes=... tested
• /ways?ways=... tested
• /relations?relations=... tested

Moved out of --enable-experimental

• /node/#
• /way/#
• /relation/#
• /nodes?nodes=...
• /ways?ways=...
• /relations?relations=...

Decide on

• HEAD requests
• Last-Modified header Should we be returning Last-Modified on single-element calls? #36

[pnorman]

Per irc conversations, we're okay responding with 405 to non-GET requests, although the error message needs fixing (no longer specific to map requests) and should probably be specific to HEAD requests so you get a different error message if cgimap gets a PUT request which is part of the API vs a HEAD which isn't a documented part.

[zerebubuth]

I've started adding these to milestone 0.3.0. I'm not sure as I've not used Github's milestone support before, but managing them that way might be easier?

[pnorman]

well, I don't have the access required to create a milestone, so that ruled it out for me

[pnorman]

The only issue remaining for 0.3.0 that I'm aware of is #39, which is about Content-Disposition. As it's driven by a website UI question, I've raised it in openstreetmap/openstreetmap-website#479 but it hasn't yet attracted any comment

[zerebubuth]

#39 is fixed by #79, so I'm going to tag 0.3.0.