Activity log for bug #1820677

Date Who What changed Old value New value Message
2019-03-18 16:43:38 Anton Shepelev bug added bug
2019-03-18 16:44:33 Anton Shepelev description I find it a nuisance that the latest revision of the main branch in not easily downloadable as a single archive. For many small and simple projects this is a sufficient release model, saving the developer the creation and upload of a source archive after every update of the source. In Github, for example, this function is within two clicks for the project's title page: 1. Click "Clone or Download", 2. Click "Download ZIP". In Launchpad, however, merely to browser the Git source the user has to: 1. Click on the "Code" tab, 2. Click "Browse the code", 3. Click "Tree". This path is longer and less obvious. Some visitors simply fail to find it, forcing the developer manually to manage source archives in parallel with the repository, whereas the system can do it for automatically. I find it a nuisance that the latest revision of the main branch in not easily downloadable as a single archive. For many small and simple projects this is a sufficient release model, saving the developer the creation and upload of a source archive after every update of the source. In Github, for example, this function is within two clicks for the project's title page: 1. Click "Clone or Download", 2. Click "Download ZIP". In Launchpad, however, merely to browser the Git source the user has to: 1. Click on the "Code" tab, 2. Click "Browse the code", 3. Click "Tree". This path is longer and less obvious. Some visitors simply fail to find it, forcing the developer manually to manage source archives in parallel with the repository, whereas the system can do it for them.
2019-03-18 17:11:35 Anton Shepelev description I find it a nuisance that the latest revision of the main branch in not easily downloadable as a single archive. For many small and simple projects this is a sufficient release model, saving the developer the creation and upload of a source archive after every update of the source. In Github, for example, this function is within two clicks for the project's title page: 1. Click "Clone or Download", 2. Click "Download ZIP". In Launchpad, however, merely to browser the Git source the user has to: 1. Click on the "Code" tab, 2. Click "Browse the code", 3. Click "Tree". This path is longer and less obvious. Some visitors simply fail to find it, forcing the developer manually to manage source archives in parallel with the repository, whereas the system can do it for them. I find it a nuisance that the latest revision of the main branch in not easily downloadable as a single archive. For many small and simple projects this is a sufficient release model, saving the developer the creation and upload of a source archive after every update of the source. In Github, for example, this function is within two clicks from the project's title page: 1. Click "Clone or Download", 2. Click "Download ZIP". In Launchpad, however, merely to browse the Git source the user has to: 1. Click on the "Code" tab, 2. Click "Browse the code", 3. Click "Tree". This path is longer and less obvious. Some visitors simply fail to find it, forcing the developer manually to manage source archives in parallel with the repository, whereas the system can do it for them.
2019-04-01 16:02:30 Colin Watson tags feature git lp-code ui
2019-04-01 16:02:35 Colin Watson launchpad: importance Undecided Low
2019-04-01 16:02:35 Colin Watson launchpad: status New Triaged