Karl/BobStore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add maxage issue to TODO

Browse Source
This commit is contained in:
Daniel Martí 2014-02-20 00:25:14 +01:00
parent 231fb3dd8a
commit 8f506c0b0b
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
TODO-before-release.md
View File

@ -1,11 +1,14 @@
These issues are a must-fix before the next stable release: These issues are a must-fix before the next stable release:
* Right after updating a repo, "Recently Updated" shows the apps correctly but * Fix updating of `TABLE_REPO` from a very old version, also known as the
`duplicate column name: maxage` issue.
* Right after updating a repo, `Recently Updated` shows the apps correctly but
the new apks don't show up on App Details until the whole app is restarted the new apks don't show up on App Details until the whole app is restarted
(or until the repos are wiped and re-downloaded) (or until the repos are wiped and re-downloaded)
* App.curVersion is now used in some places where before we used * `App.curVersion` is now used in some places where before we used
App.curApk.version, which means that e.g. app lists now show the current `App.curApk.version`, which means that e.g. app lists now show the current
version at upstream and not the latest stable version in the repository version at upstream and not the latest stable version in the repository
(highly misleading to users, who might end up looking for versions not in (highly misleading to users, who might end up looking for versions not in
the repo yet) the repo yet)