soren121
commented
9 years ago From ian.aldr...@gmail.com on June 21, 2012 20:19:48
While this is a good idea, I think it should be put off until LightBlog 1.0.
In that version I planned on making an updating system that was accessible via the control panel. When an update was available they would click a link and LightBlog would download the update for the version that comes after their current version (so if they are on 1.0.0 and the latest is 1.0.3 but there was a 1.0.1 and 1.0.2 in between, it would update to 1.0.1, they would continue this process until they're up to date).
I could also have it automatically download (in my example above) the 1.0.1, 1.0.2 and 1.0.3 updates and only extract the source files from 1.0.3 but then just extract the update.sql files from 1.0.1 and 1.0.2 and apply those before 1.0.3's.
Either way, this would mean we would only have to maintain a single update.sql file.
From doodle62 on June 21, 2012 23:06:54
Right now, the only versions that would be reasonable to support are 0.9.2, 0.9.3, and 0.9.3.1, though there weren't any database changes in 0.9.3.1.
This should be easy: just have SQL files for 0.9.2 and 0.9.3. It would be more efficient than I just made it sound.
Original issue: http://code.google.com/p/lightblog/issues/detail?id=48