Jordache
Okay guys, I've seen both sides of the story and understand where each person is coming from, however, as a site developer, people would like to start their communities with the latest features and not confuse their users with a Dolphin 6.1.6 build to a Dolphin 7.0 because the structure is different and the whole user interface is better in 7.0.

Now for the people who are using 6.1.6 can see the Dolphin 7.0 is a lot better, with more features, so they would like to get developing on the new stuff see more rather than the old technology...i.e. they would like to develop on a beta and take the risk, but also have the opportunity to upgrade per release even if its beta or not, and go up in stages to developing a good working website/community. This way they would not have to have a 'fresh' clean install per version and loose all their hard work. And it can encourage the community to test harder for bugs, because it is their OWN work, that they want their users to like and to come back.

This could also be backed up by people are paying for their hosting packages/dedi/vps and secured their domains, they see fit to use for their community and do not want them to get taken.

To end it off, I know boonex are working hard to release a good bug-free version, but its up to the developer/webmaster/administrator of the site whether to take the risk or not, so why cannot boonex allow us to make the decision for ourselves.
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.054692029953003