Updating Milestones

[namdre]

this issue should receive a comment when a milestone is created or it's date is changed.
This way people can keep track of them (as there is no other way to get automated notifications of milestone changes).

[namdre]

set date for 1.8.0 and 1.9.0

[behrisch]

I am not sure we will remember this every time we change a milestone.

[namdre]

@lcodeca wanted an issue to watch for changes so every time we do remember to update this it helps.

[behrisch]

Moving 1.8.0 to an earlier date for Vector

[namdre]

Delaying release by 1 day to deal with regression.

[behrisch]

delaying 1.9.0 due to Easter holidays

[behrisch]

adding 1.9.1

[behrisch]

fixed the date of 1.9.1

[behrisch]

adding 1.9.2

[behrisch]

fixed the date for 1.12.0 and a preliminary one for 1.13.0

[namdre]

postponed 1.13.0 by 2 weeks

[palvarezlopez]

Postponed 1.15 by two weeks

[behrisch]

postponed 1.16.0 to 31.01.

[palvarezlopez]

Postponed 1.16.0 to 07.02. due problems with DLR server (Docu and build)

[behrisch]

delayed 1.17.0 due to Easter holidays

[palvarezlopez]

delayed 1.17.0 one week due #13013

[namdre]

set preliminary dates for 1.19.0 and 1.20.0 (just so I can use them to postpone stuff to after my sabbatical)

[palvarezlopez]

delayed 1.18.0 one week due #13393

[palvarezlopez]

Delayed 1.19.0 due personPlan creation and tests

[palvarezlopez]

Delayed 1.19.0 due JuPedSim and tests

[behrisch]

delayed 1.20.0 due to the high number of regressions

[behrisch]

further delay of 1.20.0

[behrisch]

Delaying 1.20.0 until the SUMO conference

[behrisch]

Delaying 1.21.0 due to libsumo problems