CB 1.10 - roadmap pushed back (again)

Hi guys

Great work on getting the CB1.9.1 out, excellent that you solved the problem with the new J that fast, very impressive, and it certainly saved a lot of headaches!

But I can see that it also affected the roadmap for 1.10, which makes me sad
It's the #4183 feature I'm waiting for here, with much impatience
Is it getting closer? I wish I could help out with something, but I'm just not a coder, sorry.

fribse2011 wrote: Hi guys

Great work on getting the CB1.9.1 out, excellent that you solved the problem with the new J that fast, very impressive, and it certainly saved a lot of headaches!

Thanks!

Most of our effort lately went into Joomla 3.2 (app-store and usability improvements).

But I can see that it also affected the roadmap for 1.10, which makes me sad
It's the #4183 feature I'm waiting for here, with much impatience
Is it getting closer? I wish I could help out with something, but I'm just not a coder, sorry.

Yup - this happens.

You can help on the forums - this way developers will have more time everyday for coding instead of supporting.

Yes, it was pushed but folks please understand that is not a release date. It's just an internal goal to try and keep things realistic. If it needs to be pushed then it's pushed, but it's not done so lightly.

I pushed it quite a bit to give room for 1.9.1 and new Joomla bug fix releases as I don't want to release 1.10.0 then Joomla make a release, breaks CB, and have to release 1.10.1. In short I did not have much trust in some of the last minute changes to J3.2 (looking at you password encryption changes) and didn't want to risk it breaking CB and all of my hard work. In a hurry we released 1.9.1 as we discovered the Joomla password changes flat out made CB non-functional, but even then a bug in Joomla basically crippled CB (password changes in Joomla).

With all that said it could certainly release into Beta long before the roadmap date. I just got tired of pushing it 1-3 days or a week as needed. I'll reduce it once I can give a more definitive answer, but things are definitely looking good (see Issues; we're nearly there).

Also when it does release please see the release workflows as follows.

1. Beta to Developer subscribers (probably last 1 week?)
2. RC to Professional subscribers (probably last 1 week?)
3. RC to Advanced subscribers (probably last 2 weeks?)
4. Stable release made public

This gives our subscriber base fist glance as well as get in more testing and if needed bug fixes before a public release.

Hi Kyle
I'm terribly sorry if you took my post as a critisism, it's absolutely not meant that way. I'm very well aware that the date is not a 'release date' but a guideline, but patience is a virtue, and I'm a sinner
I just wanted to let you know that it's still interesting, and awaited.
I did see that there aren't that many issues left, which looks good, but even 1 issue can be tricky so the quantitative meassure could be wrong. Now GET BACK TO WORK, and stop posting