Changes between Version 138 and Version 139 of DevelopersGuide/Schedule


Ignore:
Timestamp:
2016-08-19T16:50:10+02:00 (9 years ago)
Author:
Klumbumbus
Comment:

make this page always up to date

Legend:

Unmodified
Added
Removed
Modified

  • DevelopersGuide/Schedule

    v138 v139  
    1    = Schedule =
     1= Schedule =
    22
    3 This page documents the current state of the JOSM release cycle. It might be outdated, check "next event" to be sure.
     3This page describes the JOSM release cycle.
    44
    5 The JOSM project has a very pragmatic development model, see [[wiki:Releases]] for details. Basically we are alternating between two states as described below.
    6 
    7 == Current State ==
    8 
    9 {{{#!html
    10 <table cellspacing="0" cellpadding="7"  border="1">
    11 <tr style="font-size:120%; background-color:#dbe2ec"><td>X</td><td>Free to modify</td></tr>
    12 <tr style="font-size:120%; background-color:#dbe2ec"><td> </td><td>Stabilization </td></tr>
    13 </table>
    14 }}}
     5The JOSM project has a very pragmatic development model, see [[wiki:Releases]] for details. Basically we are alternating between two states: '''Free to modify''' and '''Stabilization'''.
    156 Free to modify::
    167   This phase is for normal development. No special restrictions, but be aware, that the nightly builds are used by a lot of people. We usually get overwhelmed with bug reports when josm-latest is seriously broken.
    … …  
    189   Feature freeze, string freeze, focus on bug fixing. Sometimes minor changes are okay (especially when there is some time left till the release), but try to avoid introducing new bugs. Stabilization phase can exceed the release date by a couple of days.
    1910
    20 Usually a release is planned at the end of each month (the weekend nearest to this date).
     11The stabilization phase starts always '''a few days before a release''' (to make sure no major bug is included and to give the translators time to translate the latest strings) and ends '''a few days after a release''' (in case of a required hotfix if a major bug was part of the release).
    2112
    22 Creating a release currently simply means getting a latest version which has most of translations done and has no serious bugs. This is then marked as release a bit later.
     13Usually a release is planned at the end of each month (the weekend nearest to this date). Check the '''[[/roadmap]]''' for the next planned release.
    2314
    24 == Next event ==
    25 See [[/roadmap]]
    26 {{{#!comment
    27 <table cellspacing="0" cellpadding="7"  border="1">
    28 <tr style="font-size:120%;background-color:#dbe2ec"><td>
    29 2016-07-31
    30 </td><td>
    31 Release of <tt>16.07</tt>
    32 </td></tr>
    33 </table>
    34 }}}
     15Creating a release simply means doing a last translation update, getting the latest version and mark it as josm-tested.
    3516
    36 == Log ==
     17
     18== Log of JOSM-tested versions ==
    3719
    3820[[ReleaseLog]]