Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Updating to DNN 4.5.1Updating to DNN 4.5.1
Previous
 
Next
New Post
4/17/2007 12:15 PM
 

What surprises me is I thought Alex was in the QA team..  yet even he is confused.

Is there a QA team?

Gemini has three issues  http://support.dotnetnuke.com/project/RoadMap.aspx?PROJID=2

There is another thread talking about release process.

 

Is anyone actually managing this project?   One week, the official info is in one blog, next week another blog...       Gemini is not updated.    

 
New Post
4/17/2007 1:26 PM
 

I just help out by validating issues in Gemini, this is my main adopted role as part of the QA team. I also do point out things out from time to time which are mainly Gemini related (I pester if you like). I am not core, there's a subtle difference here, I don't play a part in taking core decisions. Quite frankly I'm quite happy about this situation at the moment.

Yes there is a QA team, and they do a lot of background work that you don't see or probably just take for granted, you just see me more nowadays because I'm the guy validating the issues in Gemini before they get looked at. I know the QA team lead does a heck of a lot of background tasks that you guys don't see. Please don't ask me to comment further as really it's not in my place to put words into other peoples mouths or make comments on people's behalf, they would not like that.

This is also open source software. You should understand that all the teams work on different time zones and locations. Some people go on holiday, some people are busy working on something else. Almost all of us are not paid to do this (yes we are all quite mad). So sometimes you just have to wait for things to come out in the wash. You should also realise that by contributing you are also in effect part of the team (this is key, do you have anything to contribute?), it's that it is just a different dynamic then say, Microsoft.

On the whole it works out quite well, but by no means perfect...  If the core team spent all their time in the forums then no work would get done. If they didn’t spend any time in the forums you would wonder what is going on. There is a balance. In fact right now I realise I have been posting too much recently, and intend to cut this right down myself!



Alex Shirley


 
New Post
4/17/2007 1:44 PM
 

The upgrade package have all modules in the install_modules folder so maybee you have go through those before extracting the upgrade zip of 4.5.1. I dont know if this is by design but I asume its by mistake..

Have tryed to get an answer in Benefactors chat but no answers yet....

 

 
New Post
4/17/2007 2:14 PM
 
As with all new releases, 4.5.1 was announced (http://www.dotnetnuke.com/tabid/825/default.aspx) throug a blog by one of the core team members (usually Cathal). As far a communiticating to the community when a new release is expected, it has always been the policy to not make any target release dates known. Whether you agree with this policy or not, it is the way releases are handled and everyone has to plan accordingly.

Also, I second Johns Mitchell's email about history showing there is alway a point/stabalization release soon after a major release. Although we do try to catch as many major/showstopper issues as possilbe before releasing (the early release to benefactors has helped) there are alway bugs that will not be caught until an application it released to the wild (there is now way to test every single use case). Personally I usually wait for 1-2 point releases before upgrading any of my production sites (local site updated every release). As in any open-source projects new versions are released quicker, and therefore each user needs to decide how they want to handle upgrading thier production sites. If you decided to upgrade every production site each time there is a release, that is your decision. Unless your sites does not need any of the fixes in 4.5.1, then don't update. As in any release you have to look at what is fixed/added to the new version add decided if you want to upgrade your production sites.

As far as Alex is concerned, he does not have any early access to pre-released versions and he finds out about new versions the same way everyone else finds out. In his current role he validates reported issues against the latest "released version" to make sure they are still issues. He also keeps an eye on all the issues and makes sure the database public data is kept clean (correct status/resolutions, etc). In addition, he has been a good source of input on how we can make the Gemini process better. Some changes have already been made based on some of his suggestions and other are planned.

S. Shawn Mehaffie
Gemini Administatration and Testing.

 
New Post
4/17/2007 2:34 PM
 

.. and I hate to get the cringe worthy "pat each other on the back" bandwagon again, but heck I will anyway because it needs to be said:

Shawn rocks! We don't hear enough of this - 1533 posts to prove it, a ton of gemini issues, and that's just the tasks you hear about ! We have a lot to be grateful for. He doesn't publicise this often enough in my view so I will (didn't mean to embarrass you Shawn, hope you don't find this too out of place :).

Normal service has resumed... :)



Alex Shirley


 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Updating to DNN 4.5.1Updating to DNN 4.5.1


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out