[OSM-dev] Auto closing of changesets in API 0.6
osm.list at randomjunk.co.uk
Fri Oct 3 16:50:15 BST 2008
On Fri, Oct 3, 2008 at 4:23 PM, 80n <80n80n at gmail.com> wrote:
> On Fri, Oct 3, 2008 at 3:54 PM, Frederik Ramm <frederik at remote.org> wrote:
>> (forgot to reply to list)
>> Shaun McDonald wrote:
>> > Should changesets automatically be closed after a period of time? If so
>> > how long?
> Why does a changeset need to even have an open/closed state? Its just a
> unique identifier for a set of changes.
It forces people to use separate changesets. Otherwise it would be
possible to create a changeset and then assign all edits to it
forever, which wouldn't be very useful. This way changesets have a
vague bound on duration (ie: how long an editing session can be kept
alive), which makes some of the fun stuff you may want to do with them
(like providing reversion) slightly more sane as you know whether new
edits can be added or not.
More information about the dev