Two weeks have passed since our first release candidate and our bug reports forum has remained steady at just a single page of unresolved bugs, most of which related to issues on which we are awaiting feedback or third party software. For the most part the inflow of bug reports has been very slow. We have fixed a silly error related to editing messages in personal conversations and a handful of other relatively minor issues.
The time at which we will declare 1.0.0 stable is approaching rapidly and our efforts are now divided between bug management and preparation of other materials to support the stable release, such as end user documentation.
All licensed customers may now download the new version from the customer area.
Installation and upgrade steps are listed below, though they remain unchanged from previous versions.
This is Unsupported Software
While we have moved on from the beta distinction, please remember that this release is not officially supported. Support is limited at this time to questions here on the community forums.
If you choose to run unsupported software, it is your responsibility to ensure that you make a backup of your data.
What is a Release Candidate?
After a number of beta releases, the functionality of the product should be complete and the rate of bugs being reported (should) slow to a trickle, allowing the development team to work through the backlog and reduce the number of bugs to a handful. We have now reached this point in the development of XenForo 1.0.0, so the time is right to produce a release candidate.
This means that the software is proposed as stable, and a period of time is allowed to verify the proposal. If no major bugs are found during that period, the software will be released as 1.0.0. If major bugs are found that are considered sufficiently important to delay the release, we will see a second release candidate. This process continues until no major bugs are discovered during the probation period for the latest release candidate.
Notable Changes
While our focus as far as XenForo development is concerned is now almost entirely on stability and preparation for release, there are a few minor changes to functionality.
Recommend / Tweet for Pages
Permission Terminology Changes
Rich Text Editor Content Styling
Recommend / Like Switch
The time at which we will declare 1.0.0 stable is approaching rapidly and our efforts are now divided between bug management and preparation of other materials to support the stable release, such as end user documentation.
All licensed customers may now download the new version from the customer area.
Installation and upgrade steps are listed below, though they remain unchanged from previous versions.
This is Unsupported Software
While we have moved on from the beta distinction, please remember that this release is not officially supported. Support is limited at this time to questions here on the community forums.
If you choose to run unsupported software, it is your responsibility to ensure that you make a backup of your data.
What is a Release Candidate?
After a number of beta releases, the functionality of the product should be complete and the rate of bugs being reported (should) slow to a trickle, allowing the development team to work through the backlog and reduce the number of bugs to a handful. We have now reached this point in the development of XenForo 1.0.0, so the time is right to produce a release candidate.
This means that the software is proposed as stable, and a period of time is allowed to verify the proposal. If no major bugs are found during that period, the software will be released as 1.0.0. If major bugs are found that are considered sufficiently important to delay the release, we will see a second release candidate. This process continues until no major bugs are discovered during the probation period for the latest release candidate.
Notable Changes
While our focus as far as XenForo development is concerned is now almost entirely on stability and preparation for release, there are a few minor changes to functionality.
Recommend / Tweet for Pages
Pages now include Facebook 'Recommend' and Tweet buttons as standard. They are automatically disabled if you have these functions turned off globally.
Permission Terminology Changes
In order to assist with intuitive comprehension of the permissions system, we have renamed two of the permission states to reflect their functions. The Default state has now been renamed to Not Set (No), and the Deny state has been renamed to Never. A tooltip has been added to the Never state, to indicate that you should use this infrequently.
Rich Text Editor Content Styling
Changes have been made to the CSS that styles the contents of the rich text editor (RTE / WYSIWYG editor) that should make it more accurately reflect the appearance of text in your messages. However, in the event that the styles you have defined are not reflected by the standard CSS, we have added a new style property to allow you to override all styling and specify exactly what you want.
It's called Rich Text Editor Content (@editorContent) and can be found in the Message Layout style property group.
Tweet Button Asynchronous Activation We had various reports of the Twitter integration slowing down page rendering times, so we have altered the script to activate the Tweet buttons asynchronously, meaning that the page rendering will not be delayed if Twitter is having a slow day.
Recommend / Like Switch
It is now possible to switch all Facebook 'Recommend' buttons to read 'Like' instead should you wish to do so.
