|
Size: 1351
Comment: Add release 19.12.
|
Size: 2333
Comment: legacy code releases
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| Fast Downward has been in development since 2003, but we only started using the current release model in 2019. Some very old planner versions from are available in a [[https://bitbucket.org/malte/downward-ancient/|repository of historical Fast Downward versions]]. | 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. /!\ '''Note that these repositories are no longer updated and do not contain current Fast Downward code!''' * 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. |
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. 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.
![/!\](/moin_static1911/rightsidebar/img/alert.png "/!\"){kind=small}
Note that these repositories are no longer updated and do not contain current Fast Downward code!
Before version control: write to Malte <malte.helmert@unibas.ch> and ask about downward-ancient
Subversion: write to Malte <malte.helmert@unibas.ch> and ask about the legacy Subversion repository
Mercurial: write to Malte <malte.helmert@unibas.ch> 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 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 International Planning Competition series.