- Aug 03, 2018
-
-
Antoine R. Dumont authored
Related T421
-
Antoine R. Dumont authored
Related T421
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
The release naming pattern is conventional, so not consistent across different packages. So it's not sane to try and enforce the order.
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
Example: ['0.1.0.dev0', '0.1.0.dev1', '5.15.0', '5.15.0.dev0', '5.15.0.dev1', '5.15.0.dev2', '5.15.0.dev3', '5.15.1', '5.15.2', '5.30.0', '5.30.1', '5.30.2']
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-
- Aug 02, 2018
-
-
Antoine R. Dumont authored
Related T421
-
Antoine R. Dumont authored
Prior to this commit, we wrongly associated the latest metadata to all retrieved releases. Now we fetch for each release the correct metadata. Related T421
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
Related T421
-
- Aug 01, 2018
-
-
Antoine R. Dumont authored
Related T421
-
Antoine R. Dumont authored
- [X] Update python dependencies (requirements*) - [X] Update debian package information (package dependency, url, description, etc...) - [X] Update copyright ranges - [X] Bootstrap README
-