Quote from: Carlton Banks on August 29, 2015, 05:47:07 PM

Suggestion (possibly devs already thought this):

Create a package that isn't "armory" for the testing releases (armory-testing?).

Rationale: the majority of users still use a monolithic OS; only one instance of a package can be installed on such a machine. There are alot of people out there who might benefit from using this upcoming test release instead of the main release, and the process would benefit from as wide a potential testing base as can be. A separate package would allow those who run release Armory to see whether 0.94, for instance, alleviates their issues or not, without having to contemplate uninstalling "armory-testing" and re-installing Armory main release.

Interesting idea. Admittedly, I'm not entirely sold on the idea of a separate package. There's too great a chance that people will be lazy and leave two copies on their system, potentially leading to weirdness down the road. For example, if somebody had 0.93-testing and tried to go back to 0.92, the Armory DB would keep getting nuked and lead to constant rebuilds.

Unfortunately, I don't think "But only people who know what they're doing will install it!" is correct. It wouldn't be hard for us to miss posts on, say, Reddit, and end up with somebody suggesting people try a test version that fixes one problem but introduces another.

(Just FYI, Reddit was just an example. Some of us do check Reddit on occasion. We typically prefer this forum, though.)

That said, it's something to keep in mind moving forward. Pros and cons, as always.