2333
Comment: legacy code releases
|
2226
Add Fast Downward 21.12 to list of releases.
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
* [[/21.12|Fast Downward 21.12]] * [[/20.06|Fast Downward 20.06]] |
|
Line 16: | Line 18: |
Fast Downward has been in development since 2003, but we only started using the current release model in 2019. Before the current Git repository, the code was first developed without version control, then with Subversion, and then with Mercurial. In case you need access to the previous repositories (for example, because your code branches off there), they are still available as read-only bundles. | Fast Downward has been in development since 2003, but we only started using the current release model in 2019. From 2008 onwards, various versions of Fast Downward and related planners were released as part of the [[http://www.icaps-conference.org/index.php/Main/Competitions|International Planning Competition series]]. |
Line 18: | Line 20: |
/!\ '''Note that these repositories are no longer updated and do not contain current Fast Downward code!''' | From 2003-2006, Fast Downward used no formal version control. From 2006-2010, the code was developed in a Subversion repository, from 2010-2020 in a Mercurial repository, and since July 2020 in a [[https://github.com/aibasel/downward|Git repository]]. The Git repository includes history dating back to 2006, but the migrations to Mercurial and to Git involved some pruning, in addition to differences caused by the different data models of these version control systems. If you need access to any of the historical code (pre-version-control era, Subversion era, or Mercurial era), feel free to <<MailTo(malte.helmert@unibas.ch, contact us)>>. |
Line 20: | Line 22: |
* Before version control: <<MailTo(malte.helmert@unibas.ch, write to Malte)>> and ask about downward-ancient * Subversion: <<MailTo(malte.helmert@unibas.ch, write to Malte)>> and ask about the legacy Subversion repository * Mercurial: <<MailTo(malte.helmert@unibas.ch, write to Malte)>> and ask about the legacy Mercurial repository * Note that Mercurial repositories compatible with the legacy Mercurial repository can be converted to Git repositories that are compatible with our Git repository. So if your repository branched off a Mercurial revision, we recommend to use [[https://github.com/aibasel/convert-downward|our conversion script]]. /!\ TODO: replace the mailto links with a published version of the bundle. From 2008 onwards, various versions of Fast Downward and related planners were released as part of the [[http://www.icaps-conference.org/index.php/Main/Competitions|International Planning Competition series]]. |
Note that Mercurial repositories compatible with the legacy Mercurial repository can be converted to Git repositories that are compatible with our Git repository. If your repository branched off this Mercurial repository, we recommend using [[https://github.com/aibasel/convert-downward|our conversion script]]. |
Back to the HomePage.
Fast Downward Releases
Fast Downward uses time-based version numbers of the form YY.MM. For example, Fast Downward 19.06 was originally released in June 2019. We intend to follow a 6-monthly release cycle, but this is not set in stone. Bugfix releases are numbered as 19.06.1, 19.06.2 and so on.
Fast Downward is research software, and we do not provide extensive support for past releases. In particular, we generally do not backport bug fixes. Bug fix releases are intended to be a rare exception to address critical problems that can be backported with reasonable effort, such as incompatibilities with new compiler versions. Bug fix releases are generally limited to the latest release series.
Releases since 2019
Historical Releases
Fast Downward has been in development since 2003, but we only started using the current release model in 2019. From 2008 onwards, various versions of Fast Downward and related planners were released as part of the International Planning Competition series.
From 2003-2006, Fast Downward used no formal version control. From 2006-2010, the code was developed in a Subversion repository, from 2010-2020 in a Mercurial repository, and since July 2020 in a Git repository. The Git repository includes history dating back to 2006, but the migrations to Mercurial and to Git involved some pruning, in addition to differences caused by the different data models of these version control systems. If you need access to any of the historical code (pre-version-control era, Subversion era, or Mercurial era), feel free to contact us <malte.helmert@unibas.ch>.
Note that Mercurial repositories compatible with the legacy Mercurial repository can be converted to Git repositories that are compatible with our Git repository. If your repository branched off this Mercurial repository, we recommend using our conversion script.