Beta 3?

I hope we see a beta 3 of 7.2 before 7.2 is released; Boonex needs to resist the pressure of "I want it now!" by some of the community.  With some of the issues we saw in beta 2 I think it would be prudent to issue a 7.2B3.for testing.

I think soo many things need to be changed in dolphin. Its better if administration here to provide us the goals for 7.2 , 7.3 and 7.4 so we won't create pressure for including extra functions in 7.2. Like andrew cleared about 2 things that would be included in 7.3 ( New chat, Like and internal sharing function). But 1 thing is must for 7.2 is the privacy concern. With out it these fancy changes are useless. Profile timeline privacy don't work how it supposed to work.

 http://www.boonex.com/trac/dolphin/roadmap

 Did you check the road map for 7.3? How many of the tickets created in there are from administration? I don't think that define the real goals for 7.3. They are just left over tickets.

Beta 3??  How about Beta 3, 4, and 5

If needed.  It is better to put out 7.2 when it is stable (of course Dolphin is under constant development as any such platform is) than to meet the whines and moans of those that keep wanting it out before it is ready.

Im demanding 7.2 now ! Where's it ? ??? I have big dollars lol

I would rather see it stable just like it is, than have to wait any longer to quit my job and make it big.

Agreed, another beta would just be discouraging at this point.

The time to fix bugs is before releasing it.  However, those demanding it now would probably be the loudest whiners if bugs were found after the release of 7.2.

Geek_Girl, remember that many modules are not compatible with 7.2 and I think I read that some developers expect the final version to update their modules, it seems to have read it. And impossible to migrate without the modules, at least for the most important. With beta 3, we are still here in six months I think ... unless major changes, and I do not think that a beta version is made for that, why b3?

We are most likely to release the 7.2 soon and follow up with service update soon after. As noted, there are a few pressing reasons for that...

- Upgrade package is needed for 7.1 to 7.2. This is the only way to really test things.

- Developers are on the fence and need a stable release.

- Suspended state adversely affects business for us and most developers. Clients are waiting, not buying.

- It's time.

This is correct, 5 to 10% of web owners cant wait and just make their  site customized.  However majority is waiting.

That really affects business.

My site is in hold at the moment , yes i can't wait , if we have 7.2 stable / even if not bug free , at least we have something better/mobile friendly and we can take it from there , this way majority of us will use and the majority of us will spot more bugs and report it here and we can all work on fixing them !

Now if you really look in the forum just few people reporting bugs not everyone so will make the process longer and if they release a B3 then it will get longer and longer and this def not good for anyone.

Release the Beast , And let us cracking on the shit of it .

Thank you

like above me. enough that it responsive its worth release.

from there on we relay on minor updates. like always

 I suspect that prudent developers would have used the latest Beta and modified their offerings already.  I will check all my main 3PM (third party modules) prior to upgrading as I cannot have my site not function properly. So I will wait a few weeks after release to see how things turn out.

If someone is putting up a new site - they should just go with the latest beta - why wait?

As Andrew said - It's Time.