Announcement

Collapse
No announcement yet.

No devs at the bugtracker?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Yves Rigaud
    replied
    That explains a bit more how they done the work on PT, thanks

    Leave a comment:


  • Lynne
    replied
    I think they go by the priority given to the bugs to determine which have to be fixed prior to releasing the next version. (At least while testing before, they would not release a new version until all priority 1 bugs were fixed. Then after the release, they would re-prioritize all the bugs and again, not release the next version until all priority 1 bugs were fixed.)

    Leave a comment:


  • Yves Rigaud
    replied
    At this time, we have for Beta 4 only:
    • 203 unconfirmed bugs
    • 64 confimed
    • 37 awaiting feedback
    • 96 fixed (pending)
    • 62 confirmed as bug scrub

    They should to see all unconfirmed and fix confirmed before releasing a new version...

    Leave a comment:


  • Yves Rigaud
    replied
    I hope this is a joke...

    Leave a comment:


  • RS_Jelle
    replied
    I see you guys are preparing RC1? You must be joking? There are almost 1500 open bugs now?

    Only 248 of them are confirmed/bugscrubbed and have a 4+ priority. I can't believe all other 1218 bugs aren't important enough to get fixed before going gold?

    Leave a comment:


  • Steve Machol
    replied
    Also there is an explosion of bug reports since the Beta went public. This is entirely normal.

    Leave a comment:


  • Wayne Luke
    replied
    Many of those open bugs will be duplicates. Some will not be high enough priority to prevent a final release and a number are actually suggestions which will probably get lower priority as well.

    Leave a comment:


  • RS_Jelle
    replied
    Looking at the public bugtracker, we reached a new record: 1000+ open bugs.

    At the moment I'm seeing a lot of status changes to confirmed (and the new "bug scrub"), but why are there so little status changes to fixed?

    Getting a gold release before the end of this year, with all bugs fixed, seems to become more and more difficult. Although, this is not bad IMO. Personally I'm more interested in a QA release with all bugs fixed and some highly asked suggestions included (like custom CMS pages and a better search and asset manager GUI). If people want it faster, they can get the public beta's.

    Leave a comment:


  • pank
    replied
    My only suggestion regarding the bug tracker is this. If the person reading a bug post notices that the post may not contain a common search term maybe it should be added to the bug post to avoid duplicates and save the Dev's / bug checkers time.

    Just an example: I saw a bug at the top of the what's going on box where the border on the left and right extended over the top of the box where it should not be. I did a search for what's going on and found no results so I posted the bug. It ended up being a duplicate bug report because the original post used WGO as an abbreviation and I never thought to search for that term.

    Just an idea to help.

    Leave a comment:


  • Steve Machol
    replied
    Honestly the Devs are not going to post a response to every bug report. Check the status of your bugs to see if there have been any changes. I assure you that Bug reports are being scrutinized every day via the daily bug scrub.

    Leave a comment:


  • rEd86
    replied
    Originally posted by Steve Machol View Post
    One bug tracker is available only to the Alpha/Beta testers and contains info that should not be shared publicly. Also no one ever said to hold off reporting bugs. Quite the opposite in fact.
    Originally posted by Steve Machol View Post

    This will be resolved when the Beta is released to all pre-sales customers.
    I would think that you could segment what's viewable with security groups, but that's a non-issue since we'll all be on the same platform shortly.

    While no one said to hold off on reporting bugs, we are also not getting any feedback on the bugs we are reporting. It's good to hear that everything is getting looked into that is getting reported, but it would be nicer to see the status change on the bugs that we are reporting. Even seeing a list of bugs that were resolved with each beta release would be beneficial.

    We are all on the same team and want to see a great product. We're just trying to improve the process so we're all more efficient.

    --Ed

    Leave a comment:


  • Steve Machol
    replied
    Originally posted by rEd86 View Post
    This confuses me - why continue to have two bug tracking systems?
    One bug trackere is available only to the Alpha/Beta testers and contains info that should not be shared publicly. Also no one ever said to hold off reporting bugs. Quite the opposite in fact.

    This will be resolved when the Beta is released to all pre-sales customers.

    Leave a comment:


  • Zachery
    replied
    If they're being reported they are being looked into.

    Leave a comment:


  • rEd86
    replied
    Originally posted by Zachery View Post
    Do not hold off any bug reporting please.
    OK, as long as we're providing value. I guess I'm going to have to dig into the system a little more and see if I can figure out if I'm overlooking something since I am not seeing much staff activity/feedback in the public bug tracking system. (or just change my expectations and just keep beating things up)

    Thanks again for the hard work.

    --Ed

    Leave a comment:


  • Zachery
    replied
    Do not hold off any bug reporting please.

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X