I have not done an upgrade but here is what I have on DNN 3.3.6 and Events 3.02 (nearly a year old...but the latest) and it really needs to be fixed.
I created a recurring event for the 1st Wed of each month at 7:30PM. The first one is on 1/3/2007. Here are my results.
Calendar renders the event on Thur (1/4), but at the list it shows the incorrect Time Zone and the time is 12:29PM.
MouseOver shows the event on Thur (1/4) and at 12:29PM also
Click of event and the detail page shows Fri (1/5) at 12:29PM and the Time Zone is wrong as well. It does at least say First Wed of every month.
I have another recurring event that is based on every 20 days on a different Events module instance and it seems to work.
The AVCal, which I assume is the source for the "new" events module has been around for ages. I did a lot of testing and feedback for Alan since early DNN 2. What I cannot figure out is why we cannot get a simple DNN CORE Calendar (or Events or whatever it needs to be called) module that just works...with recurring events. This is not a slam on any particular individual, but what can be done to make this work. For people trying to build a business around DNN, which I have been trying to do since late 2002, the CORE modules need to work...especially something as common as a Calendar module. Sure I can handle some issues as a web developer on my personal sites, but how can I turn DNN on to a large market and then say...Don't use the Events Module..or the Gallery Module...or whatever, since they don't really work. I realize that third party modules can be used to fill gaps in functionality and I use a good number of them from the top developers. But I should not have to use a third party module to do something that is contained within a CORE module but does not even meet the basic level of advertised functionality.
Sorry for the RANT, but we really need something that works. I have shown my support as a Gold Benefactor, and sure I would be willing to maybe pay out a little to get some things done, but what I don't like is to see all these advanced functions being added to a CORE module, when the existing, necessary functions don't work correctly.