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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumNot to beat a dead horse but...Not to beat a dead horse but...
Previous
 
Next
New Post
5/15/2008 2:54 PM
 

RE: Core forums - All I have to say in reply is if thats the SOP then than why even bother? Even a hobby that is depended on by others needs some level of quality and work ethic.

RE: Activation - As I said thankfully I have a older ver of active forums right before they included the activation. I'll simply use that it looks like. Granted not many people do as many wipes and reinstalls as I do but there has to be a better way. I am not opposed to a serial #, activation or the like mind you, just their execution of it I take issue with.

 
New Post
5/15/2008 2:56 PM
 

Matthias Schlomann wrote

It is a problem to support public beta versions.  Then it need more longer to get any bugfixes, about the project team is not on develope, they are then on supporting costumers issues.  Is this what you want?  Betas will only given to special testing teams, with members that obligedet to test and reply results.  You are free to use 3rd parity module.



Apparently you did not read what I posted, I'd encourage you to go back and read what I said about a *NO* RC support model then reply to that.

 
New Post
5/15/2008 3:22 PM
 

Strauss wrote

RE: Activation - As I said thankfully I have a older ver of active forums right before they included the activation. I'll simply use that it looks like. Granted not many people do as many wipes and reinstalls as I do but there has to be a better way. I am not opposed to a serial #, activation or the like mind you, just their execution of it I take issue with.

Active Forums Enterprise allows you to have as many test installations as you like.  Over the past year we have made several improvements to the activation process and requirements.  We have also made it much easier to move from server to server and keep your license activated.  It's unfortunate that we had to add license activation.  However, even though our license, like many other modules, has always been for a single DotNetNuke installation, it's amazing how few people actually read the license terms.  Customers that didn't understand the license policy have bought additional licenses.  While others that wanted to take advantage of the lack of enforcement for the license decided to stay with previous, unsupported versions. 

Activation really isn't that bad.  All we are trying to do is make sure you are not running your production license on multiple DotNetNuke installations.  We are also adding some additional features to our site that will allow you to better manage your licenses. 

Feel free to email me directly if you have a suggestion as to how we could better handle activation.

willm ~ at ~ activemodules.com


Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
5/15/2008 7:29 PM
 

Strauss wrote

 Matthias Schlomann wrote

 

It is a problem to support public beta versions.  Then it need more longer to get any bugfixes, about the project team is not on develope, they are then on supporting costumers issues.  Is this what you want?  Betas will only given to special testing teams, with members that obligedet to test and reply results.  You are free to use 3rd parity module.

 



Apparently you did not read what I posted, I'd encourage you to go back and read what I said about a *NO* RC support model then reply to that.

The problem is that users who used a public Beta or RC did not hold on the agreements of the use of those versions.  It can not be handled from the Team to support questions of thiese version on this forum.  It is also if you use other software and it needed a fix, you have to wait between a fix is creating and tested well. 

We have our conditionswith quality assourance of the DotNetnuke Coperation, and we have to holf byself on there defaults.  All users are free to help in any DNN teams, also as in a beta testing group.  There it is possible to mange testings and it is clear to manage the testing.

Personaly I see that many of the users want to use the betas and RC before its released, but thy to often used it in production environments and then we have to solve there issues.  Thats not the deal.  We have to mange the testing in seperate limited testing teams.  So we are prevent for it, and it forces the work. 

The Forum Module is a very big Module and have a limit manpower, so the developement need sometimes more time.  It's open source.  And it is not helpfull to press to release a public beta version of a module.  I am not prepared to discuss this longer as it  need.  We have more then one threads about this topic on the forums.

At least, we never released public betas or RC!

 
New Post
5/27/2008 1:38 PM
 

Matthias Schlomann wrote

 Strauss wrote

 Matthias Schlomann wrote

 

It is a problem to support public beta versions.  Then it need more longer to get any bugfixes, about the project team is not on develope, they are then on supporting costumers issues.  Is this what you want?  Betas will only given to special testing teams, with members that obligedet to test and reply results.  You are free to use 3rd parity module.

 



Apparently you did not read what I posted, I'd encourage you to go back and read what I said about a *NO* RC support model then reply to that.

 

The problem is that users who used a public Beta or RC did not hold on the agreements of the use of those versions.  It can not be handled from the Team to support questions of thiese version on this forum.  It is also if you use other software and it needed a fix, you have to wait between a fix is creating and tested well. 

We have our conditionswith quality assourance of the DotNetnuke Coperation, and we have to holf byself on there defaults.  All users are free to help in any DNN teams, also as in a beta testing group.  There it is possible to mange testings and it is clear to manage the testing.

Personaly I see that many of the users want to use the betas and RC before its released, but thy to often used it in production environments and then we have to solve there issues.  Thats not the deal.  We have to mange the testing in seperate limited testing teams.  So we are prevent for it, and it forces the work. 

The Forum Module is a very big Module and have a limit manpower, so the developement need sometimes more time.  It's open source.  And it is not helpfull to press to release a public beta version of a module.  I am not prepared to discuss this longer as it  need.  We have more then one threads about this topic on the forums.

At least, we never released public betas or RC!



Then frankly thats YOUR failure to not stand your ground. If you state 'heres the RC, as is, we will not support it but want you to report bugs' then thats that. No one is holding a gun to your head to give them support which you stated. If you did that then you simply say 'sorry' and close the thread. It's that simple and how most other s/w devs do it. It seems you are just making excuses and a mountain out of a mole hill for some reason. Your logic is VERY faulty and you simply are not making any rational sense.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumNot to beat a dead horse but...Not to beat a dead horse but...


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