For anyone wanting to check this out, there's a default guest view available and/or you can create an account.
Preferably you would note if Mikrotik have confirmed your bug so it can be marked as "confirmed". Default view is for RouterOS v5 however you can also submit bugs for v4,v3 and the Dude v3 and v4beta. If you're following up with Mikrotik on a bug you've encountered, assign the bug to yourself so people know you're working with them to get it resolved. I'll create a full list of basic instructions however if anyone has any questions feel free to email me directly. Kind Regards, Andrew Cox Senior Network Administrator AccessPlus / BigAir Universe Broadband www.accessplus.com.au | www.bigair.com.au On 23 May 2011 00:06, Andrew Cox <[email protected]> wrote: > And so it begins.. seeing as no-one else had jumped on it yet, I've had a > US server provisioned and now have a site up under: > > http://bugs.mikrotik-routeros.com/ > > I must admit I'm still disheartened that it's come to this, yet I've myself > discussed paid support options / issue visablity with Mikrotik yet wasn't > even given a price point wherein they'd consider it. > > Anyone who's either: interested in assisting with the initial bug > confirmations, or is interested in assisting in other ways is welcome to > chime in (email me on or off list) and I'll do my best to address all > concerns and weigh up all ideas publicly or privately as requested. > > Kind Regards, > > Andrew Cox > Senior Network Administrator > AccessPlus / BigAir Universe Broadband > www.accessplus.com.au | www.bigair.com.au > > On 18 May 2011 23:53, Sam Tetherow <[email protected]> wrote: > >> I haven't worked much with wiki's other than a simple mediawiki install >> for keeping notes and such, my question would be is there a easy way to >> search it for bugs? >> >> One nice thing about bug trackers is the tuning you can do on the search, >> such as major/minor revision numbers, bug status, keyword searches. >> >> Of course then again, if this is only a user end of things maybe these >> fields will not be all that helpful since we have to assume we are not going >> to get any developer input from MT, which really is sad. >> >> >> On 5/18/11 1:30 AM, Butch Evans wrote: >> >>> On Tue, 2011-05-17 at 09:31 +0300, Chupaka wrote: >>> >>>> I think, it should be either forum or wiki. >>>> >>> Personally, I lean toward a wiki, too. It looks like people want >>> SOMETHING that will permit "us" to keep up with what works and what >>> doesn't and which version is affected. The problem I see with a real >>> bug tracker is that there would be no way to easily close bugs. There >>> is no way to see if something was fixed (even if it's in the changelog). >>> For this reason, I think a wiki would be better. I'm not sure how it'd >>> need to be organized to make it a good bug tracker, though. I'm open to >>> any ideas and input. I can have something set up this weekend. >>> >>> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://www.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.butchevans.com/pipermail/mikrotik/attachments/20110523/9c620ce5/attachment.html> _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
