Rollover policies

[NinjaTrader_JoshP]

cshep,

Unfortunately there is no public list. As the turnover time between each beta is relatively quick, there is generally no need to run a list. Furthermore, we actually prefer it if you reported any and all issues you experience as that can help us gauge the scope of the issue. In this particular issue it may not be a big help as we know it affects everyone, but for other issues it helps us isolate issues when we can pull analysis from multiple customer bug reports.

The update page is updated every once in awhile when milestones are met. For more detailed information on the progress of the beta you can find them in the various beta emails as new versions roll out.

The Help Guide is a work in progress. Priority is ironing out bugs. In the meantime, if you have specific questions about how to do certain things please post them in a new thread in these forums and a tech rep will respond to you with information on how to achieve it. Thank you.

[Acqua]

Acqua,

It is never our intent to not be straight forward. The answers provided to you were 100% accurate and fully disclosed all information at the time of your posting. It became a known issue well after you posted, but before Harry posted.

Josh,

Never questioned ill intent. We're both doing our part (i find bugs, you fix them) in trying to get NT7 out soon.

I browsed the forum, didn't find anything relevant to my issue then created the thread. Very very shortly afterward i find Harry's thread with my same issue classified as KNOWN issue.Very difficult to know the timing if/when bugs become known issues.

Don't know if there's a public central repository of Known issues, so testers can use it as reference and only new bugs are reported. If there isn't one it might be a good idea to be implemented.

Perhaps an "official bug # xxx thread" linked to each bug in the list, so people can post accordingly and both NT programmers and testers have the info relevant in one same place.

The really important thing is that you are aware of the bug and working on it.

Thanks

AQ

Edit:
Josh,
Don't want to beat the dead horse...I drafted this reply and had to leave in a rush before i could finish/post it...i just read the previous poster after posting this comment...a nice coincidence as i am not alone in my suggestion.

[NinjaTrader_JoshP]

Thank you for your comments, but currently there is no public repository for the reasons in my previous post. It will take us a lot of manpower to constantly update the status of it and we find it more efficient to just fix the bugs and roll new updates when available. Thank you for understanding.

[cshep]

I have to admit that I'm disappointed you're not going to follow through with any of the suggestions in this post. When you have multiple customers suggesting the same thing, you think that would carry some weight. Apparently not.

Beta testing has been going on for almost half a year now with no end in sight. Every time a new release comes out the notes say that merging issues have been fixed. Yet there are still bugs in merging contracts. You can't call that efficient. You think implementing our suggestions would take too much manpower. It also takes a lot of manpower to write and respond to all these posts.

I just recently started beta testing NT7. Unfortunately, I don't have the time to continue with this, especially if you're going to ingore your customers suggestions. We don't get paid to help you.

In the meantime, I'm going back to NT6.5.

Good luck with NT7. I'll check back in another 6 months or so.


CS

[NinjaTrader_JoshP]

cshep,

Thank you for your feedback. Suggestions are always taken seriously and all posts and comments are always read and noted. It is not our intention to make you feel that your suggestions are ignored.

The workflow model we are currently employing, albeit may not necessarily be the most efficient for you as a tester, is extremely efficient for us to acquire necessary information from multiple sources to reproduce bugs with. This greatly expedites our ability to isolate and address bugs. Another reason we do not employ a master list is that we find it very commonplace that one tester may think their issues to be the same as another tester's, but when we dig into it, it turns out to be a completely different concern. When the tester is the one making these judgment calls and deciding not to post a report because they saw what they thought was a known issue in a master list means we would not get any indication of this separate bug and that undesirably slows down the beta process.

That being said, beta testing is a completely voluntary process and you should not feel obligated to put up with it in any way. We hope you will be able to find NT7 a significant step above NT6.5 when we make it out of beta though. Thank you for your efforts.

[NinjaTrader_Dierk]

Let me try to clarify:
- we are aware that the beta phase takes longer than some of you guys would like to have it (including me personally)
- for that matter we decided to hold off adding any features since that even would delay NT7 further
- the merging issues are actually quite tricky and take more iterations than we had expected. Nevertheless they needed to be addressed as they are reported (or revealed by our own staff) which takes it's time as merging is part of the "critical" core of NT7
- we're still an a non-public beta for that very matter. Although I understand your frustration it needs to be understood that (serious) issues would and will arise. For that matter your decision to go back to NT6.5 is the right one for you.

Thanks everyone for your continued support and patience.