wp1
wp1 copied to clipboard
openzim
The 'release update' is currently disabled
The old bot had logic for updating the releases table in the wp 1.0 database. This code is currently not running. It has not been ported over to the new lucky bot and it's unclear if it is needed or not.
@walkerma Do you know why we had this feature? What was it doing in detail? Do you think this is a problem to get rid of it?
Please see my answer to no. 19. It was for keeping track of new 1.0 series releases, but it's probably not needed in the new bot (and I'm probably the only person besides you who would care!).
I suspect we could close that one. Not because we want to stop to make release but because:
- The selection creation process is for the moment externalised in openzim/wp1 repo
- When we will bring it back - hopefully - it will look really different whatever happen exactly
- Goal being to allow user to create their own selection, the WP1.0 releases will be only one of them.
@walkerma @audiodude Agree? Should we delete the whole releases?
@kelson42 I think deleting the releases table makes sense in theory, but I would be hesitant to do it while the old tool is still running.
@audiodude What is still on our way to stop the old WP1 engine? I have thefeelingyou have aready solved the blockers.
@kelson42 I think we could put in the redirect from the old tool to the new tool in the coming weeks, and then I just picked October 15th as the shutdown date arbitrarily, but I think we're on track for that date.
There were some initial reports on the WP 1.0 talk page about some missing features in the new tool, but I have addressed most of them.
@kelson42 I think the only feature I haven't implemented yet in the new tool is #206.