Welcome to the final Alpha release of Invision Community 5!
Itās the final alphaā¦
Yes, that time has finally come. Two alphas after the last time I said this. But this time I mean it! If you want to know what was changed, the release notes are here. Weāve now moved the Bug Tracker to our support forums ahead of the beta, so please report any issues there.
The hold up was due to an optimisation branch to reduce what was a silly amount of queries per page. We wanted this to go into an alpha as thereās a lot of changes, and we didnāt want the first beta to be obviously broken. It doesnāt set the right vibe. š«
Why so many alphas?
Iāve seen this question pop up a lot, and itās a valid question. Weāre on Alpha 16. Thatās a pretty big number. We started releasing alphas 14 weeks ago, so weāve averaged just over 1 release a week. Does this mean that itās been a really bad process and something has gone terribly wrong? Absolutely not! Version 5 has a brand new UI, brand new CSS, loads of new and rewritten JS, loads of new features, a new editor, a new page builder, and so on. Thatās a lot to not only test to make sure there are no bugs, but also in terms of feedback from testers. Weāve made a lot of changes over the past 14 weeks based on that feedback. We also decided to make sure we kept releasing alphas as often as we could. We didnāt want to wait 3-4 weeks before each release.
When we move to beta, it is to signal the end of new features, large refactors and any potential u-turns or revisions to existing new features. We want beta to just be about bugs, bugs, bugs and not introducing new ones by adding surprise new features.
In terms of stability, I am completely confident that you could use this alpha on your production community and be totally fine. I know this because weāre using it on a few private sites internally.
You may consider an alpha to be a raw and largely untested piece of software, but with Invision Community 5 it is not the case. Itās very polished and very well tested already so weāre hoping for a very short beta testing phase. Itās more akin to an early ārelease candidateā than rough and ready product to be beaten into shape.
We could have released 6 alphas and 8 betas, the labels arenāt that important.
Now is the time to move into beta though as all the heavy lifting and major testing has been completed.
Iāll do a wrap up blog post on our main site to review a few newish features that we havenāt announced yet (but youāve been using here for ages now).
Welcome to the final Alpha release of Invision Community 5!
Itās the final alphaā¦
Yes, that time has finally come. Two alphas after the last time I said this. But this time I mean it! If you want to know what was changed, the release notes are here. Weāve now moved the Bug Tracker to our support forums ahead of the beta, so please report any issues there.
The hold up was due to an optimisation branch to reduce what was a silly amount of queries per page. We wanted this to go into an alpha as thereās a lot of changes, and we didnāt want the first beta to be obviously broken. It doesnāt set the right vibe. š«
Why so many alphas?
Iāve seen this question pop up a lot, and itās a valid question. Weāre on Alpha 16. Thatās a pretty big number. We started releasing alphas 14 weeks ago, so weāve averaged just over 1 release a week. Does this mean that itās been a really bad process and something has gone terribly wrong? Absolutely not! Version 5 has a brand new UI, brand new CSS, loads of new and rewritten JS, loads of new features, a new editor, a new page builder, and so on. Thatās a lot to not only test to make sure there are no bugs, but also in terms of feedback from testers. Weāve made a lot of changes over the past 14 weeks based on that feedback. We also decided to make sure we kept releasing alphas as often as we could. We didnāt want to wait 3-4 weeks before each release.
When we move to beta, it is to signal the end of new features, large refactors and any potential u-turns or revisions to existing new features. We want beta to just be about bugs, bugs, bugs and not introducing new ones by adding surprise new features.
In terms of stability, I am completely confident that you could use this alpha on your production community and be totally fine. I know this because weāre using it on a few private sites internally.
You may consider an alpha to be a raw and largely untested piece of software, but with Invision Community 5 it is not the case. Itās very polished and very well tested already so weāre hoping for a very short beta testing phase. Itās more akin to an early ārelease candidateā than rough and ready product to be beaten into shape.
We could have released 6 alphas and 8 betas, the labels arenāt that important.
Now is the time to move into beta though as all the heavy lifting and major testing has been completed.
Iāll do a wrap up blog post on our main site to review a few newish features that we havenāt announced yet (but youāve been using here for ages now).
Thanks for your patience. š