Important Not Receiving Email Notifications

This is exactly why I want to wait for the official release of 2.0 since I feel it will reduce the chances of introducing any additional problems with the new version.

I've had a sandbox site in the past but not at the present. I use Akeeba backup so if absolutely necessary, I could decompress a jpa archive in a subdirectory but for now I'll wait for the 2.0 release. What is the best time estimate for it?

*** Off topic ***

It would be better to have discussions about K 2.0 in a different topic from this one. Seeing as you want to rigorously pursue a discussion about the schedule for K 2.0 and what you can/might/must do when K 2.0 "happens" I suppose we can indulge this for a while longer.

If you have a sandbox/test site now then, when the K 2.0.0 stable version is released it should only take you a hour to verify that everything is all right. We estimate that K 2.0.0 will be released (barring major mishaps, etc.) very soon - two weeks - after K 2.0.0. RC2. Even with the cautionary advice that we always issue to people who use RC versions, we do not anticipate introducing any changes between the RC version and the final public release; that's not say that further changes will not be introduced, of course.

Therefore, to "cut to the chase", a test/sandbox site is always necessary to have on hand. It usually takes about one hour to build one.

You should not build a test site by simply decompressing a .JPA file into a folder (or a sub-folder of your current domain) because a test site needs to have its own database. You need to keep the test database quarantined from your production. If your test site shares the same database as your production site, changes on your test site could seriously compromise your business-as-usual operations. The database for K 2.0 is structurally different to the database to K 1.7; the upgrade process makes structural alterations to an existing K 1.7 database. Please read through the release notes for K 2.0.

We recommend that people not wait for K 2.0.0 stable to "happen" but that they download and install a release candidate or beta version of K 2.0.0 on a test site in order to evaluate (a) the upgrade process, (b) the overall reliability, and (c) the differences between K 1.7 and K 2.0. The sooner that people expose themselves to any potential issues, and the more experience that people gain, there will be a lower chance of people reporting problems on the day when K 2.0 stable happens.

*** On topic ***

What we - all of us - need to know is whether or not your current email problem is fixed with K 2.0. The sooner that we find out that information, the better for everyone.

I agree with @sozzled, it would really be great if everyone tried their test sites with Kunena 2.0 rather now than after the stable release as now you can get the fix in days -- rather than waiting a month or two.

Kunena 2.0 RC2 seems to be fairly stable in our test sites, but we all know that there are bugs we haven't been able to trigger. We just haven't tried Kunena in every possible environment out there. And for that we need people to test it and report back to us from their findings (even if everything is OK).

Matias:

How close would you estimate we are now to the official release?

I can answer for Matias (because every time he is asked to answer this question on the forum, it's 5 minutes less time that he has to finishing the product). We are now in the final stages of testing K 2.0 stable. The answer to your question is the same as I gave last time you asked your question: "very soon".

We wanted to leave K 2.0.0 RC2 for two weeks to allow people time to give it the best possible exercise. When K 2.0 public is released there will, no doubt, be a few teething problems. The first expected maintenance release (which will probably be called K 2.0.1) that fixes problems/defects in K 2.0.0 will probably occur about a month after the initial product release date. This month's time will be needed to work on other matters including the migration of the site to J! 2.5 and the creation of other facilities to assist the project.

Therefore, if you would like to examine K 2.0 as a contender for resolving your email notifications issues, now is the time to do that. If you find that K 2.0.0 does not address your needs then you may be waiting a little longer while we deal with the initial onslaught of questions that will inevitably arise and consume most of our time.

It's a quiet time for us now so I suggest you use this opportunity to the fullest.

After further consideration, I've decided to wait for the official release of 2.0.

Sincerely,
Howard