unless we do a repartition release with no other changes, it would be a good
idea to do this at the transition time, going back several releases.
David Lang
1 Like
Is it possible to do a poll on this site? Maybe it could go out in the newsletter requesting that people fill it out with a single question:
Have You Ever Downgraded Your Maslow Firmware?
- Yes
- No
0
voters
Framed with something in the newsletter like:
As we prepare to expand Maslow storage space, we’re considering a few options to accommodate as many usage styles as possible. Please answer this single question poll to help…
there are a lot of users out there who never login to the forums and won’t see
the question.
we know it happens, we don’t have any idea how common it is.
David Lang
2 Likes
It’s only when an upgrade causes unforeseen problem. So it doesn’t mean much. After correction the next upgrade still goes ahead.
1 Like
That’s why I thought it might be nice to include in the newsletter? Even if only 1 out of every 10 users responds, it might provide a representative sampling/solid sense of how important providing large file system compatible older releases is… Providing additional older releases has the benefit of potentially supporting unexpected use cases, but it also has the detriment of making things much more confusing.
If it’s at all possible to provide a single, clear message, like
version 1.0 repartitions Maslow to make use of additional space.
full-install.bat/sh/commandis the bridge between releases prior to 1.0 and after 1.0. You MUST runfull-install.bat/sh/commandto go from a version less than 1.0 to 1.0 or above.full-install.bat/sh/commandwill completely erase your Maslow. Please backupmaslow.yamlbefore runningfull-install.bat/sh/command.
it seems like it would be the most digestible. The longer the message is, the less likely it is that people will read it.
It also seems reasonable for users who wish to downgrade to build their desired release themselves?
1 Like