July 1, 201610 yr 6.1.9 is quite good, but I'm hoping we'll get a 6.1.10 release to make a truly solid platform for people as they wait for 6.2 Here are the key fixes I think a final 6.1 release should have, have I missed any? * New users continue to have problems with spaces in their Docker mappings, so incorporating the latest webgui out of the box (without needing to update plugins) would be a big help. https://lime-technology.com/forum/index.php?topic=47185.0 * update-smart-drivedb needs to be fixed to use the correct url, and unRAID should ship with a current drivedb.h. Without this, some systems can become unstable. https://lime-technology.com/forum/index.php?topic=47386.msg476482#msg476482 * Parity check history should include the year, just like it does in 6.2. The longer we go without this fix, the more data there will be to cleanup. https://lime-technology.com/forum/index.php?topic=49543.0 * This last one is harder to justify because it is a feature, not a fix. But it would be a big help for the overall unRAID ecosystem because it would make it easier for plugin developers and testers to run 6.1 in a VM on their 6.2 systems. The request is: once the kernel param 'unraidlabel' is fixed for 6.2, back port it to 6.1. https://lime-technology.com/forum/index.php?topic=49705.msg476753#msg476753 Are there any other key fixes from 6.2 that need to be backported to have a really solid final 6.1 release?
July 1, 201610 yr It is very rare (never?) to see a follow up release after a new beta series is started unless there is a serious bug or security fix. Several have been promised, none that I remember ever materialized, they just faded into obscurity. Maybe the new company dynamic where Tom isn't the only developer may change things, but I wouldn't hold my breath. Witness the fair number of JonP posts where there was a complaint about 6.1.x and the response was "It's fixed in 6.2 beta"
July 1, 201610 yr I agree... I wouldn't hold my breath... unRaid is no different than a lot of other software out there. * New users continue to have problems with spaces in their Docker mappings, so incorporating the latest webgui out of the box (without needing to update plugins) would be a big help. https://lime-technology.com/forum/index.php?topic=47185.0 This however, I wholeheartedly agree with. the latest stable (whether its 6.1.x or 6.2.x) download should ALWAYS include the latest dynamix webUI update. Bump the OS version up by a point if you want, but include the official file that has all / most of the bug fixes to date for that rev. Either that, or include an auto-update feature (similar to CA's auto update) for the GUI specifically. Solves a ton of problems. All this being said, a lot of the fixes for 6.2 / 6.1.9 can be handled via the webUI, and the webUI is available as a separate update. As a matter of fact, the webUI for 6.2 is at 2016.06.11 whereas the webUI for 6.1.9 is at 2016.06.18 which means that a number of fixes were indeed backported to 6.1.9 I would assume that as the 6.2 series matures even further, the webUI will wind up being completely OS agnostic and any fixes on one automatically get backported to the other.
July 3, 201610 yr Author It is very rare (never?) to see a follow up release after a new beta series is started unless there is a serious bug or security fix. Interesting, I didn't realize that's how it worked here. I assumed we'd always want to finish up with a bug fix release.
Archived
This topic is now archived and is closed to further replies.