If there's a way to authorize MT certified individuals, I think they should be notated as such in the public bug tracker system under consideration. I like the idea as it will add legitimacy to those posts/comments in the bug tracker and I would be surprised if MT didn't take notice and use "our" system at the very least as a reference tool. The would be slightly ignorant not to.
Dylan On May 17, 2011, at 5:48 PM, Tristram Cheer wrote: > Mikrotik time and time again have stated there will be no public bugtracker > and that changelog's are as good as its going to get. > > I even spoke to them at MuM about this and they stated that MT consultants > may get access to priority support but they have no plans for people outside > of MT to have a central bug trackers or known issue list. > > Hence my frustration and this Idea > > On 18 May 2011 09:07, Andrew Thrift <[email protected]> wrote: > >> Maybe Mikrotik could allow "bug tracker" access only to people with current >> Mikrotik certification, allowing people with MTCNA to log Priority 3 >> tickets, and people with one of the MCTRE/MTCWE/MTCINE to log Priority 1 and >> Priority 2 tickets. >> >> This would limit the amount of PEBKAC tickets and encourage people to >> become certified. >> >> >> If they are completely unwilling to do something, then I agree that >> something is needed for power users to be able to see known/confirmed bugs >> for a particular RouterOS version. >> >> >> >> >> Regards, >> >> >> >> >> >> >> Andrew >> >> >> >> On 18/05/2011 3:55 a.m., Andrew Cox wrote: >> >>> Perhaps an invite-only system would be the way to go? >>> >>> Personally I feel the right thing to do here is give Mikrotik the >>> suggestion >>> and opportunity to offer something, if they're not interested then go >>> ahead; >>> I'd contribute. >>> >>> I've already approached and discussed the option of paid corporate support >>> with them (which they feel they can't justify at this time) however >>> a definitive listing of known issues (to avoid) and/or workarounds would >>> be >>> invaluable in the absence of the other. >>> >>> Kind Regards, >>> >>> Andrew Cox >>> Senior Network Administrator >>> AccessPlus / BigAir Universe Broadband >>> www.accessplus.com.au | www.bigair.com.au >>> >>> >>> >>> On 18 May 2011 01:15, Jon Paul Kelley<[email protected]> wrote: >>> >>> I agree. There is no sense in each one of us having to rediscover the >>>> wheel, if one of us already have discovered it. A bug tracker is the way >>>> to >>>> go. >>>> >>>> Great suggestion. >>>> >>>> >>>> >>>> On 5/17/2011 10:44 AM, Andrew Cox wrote: >>>> >>>> Ahhhh so it's SNMP that's causing the crash. :-D >>>>> Makes sense now! >>>>> >>>>> But yes, I agree there's something that's needed. >>>>> I can understand that mikrotik may not want everyone to know about every >>>>> little bug that comes across their desk, that said.. we need to know >>>>> what >>>>> the causes are so we can avoid them. >>>>> >>>>> Kind Regards, >>>>> >>>>> Andrew Cox >>>>> Senior Network Administrator >>>>> AccessPlus / BigAir Universe Broadband >>>>> www.accessplus.com.au | www.bigair.com.au >>>>> >>>>> >>>>> >>>>> On 17 May 2011 21:38, Jon Auer<[email protected]> wrote: >>>>> >>>>> Bugtracker++ >>>>> >>>>>> With many bug trackers you can tag a problem as being specific to a >>>>>> version (or range of versions). That could be handy for finding >>>>>> versions that are workable. >>>>>> >>>>>> >>>>>> On Tue, May 17, 2011 at 2:35 AM, Tristram Cheer >>>>>> <[email protected]> wrote: >>>>>> >>>>>> I'm not so sure, the forums are difficult in that they have a low SNR, >>>>>>> A >>>>>>> >>>>>>> bug >>>>>> >>>>>> tracker is better suited to being able to confirm bugs (via submitted >>>>>>> exchanges with MT support confirming them) >>>>>>> >>>>>>> On 17 May 2011 18:31, Chupaka<[email protected]> wrote: >>>>>>> >>>>>>> I think, it should be either forum or wiki. Because in that place the >>>>>>> most >>>>>>> important thing will be accumulating information about known bugs in, >>>>>>> >>>>>>>> mostly, previous versions - actual bugs of current version are easily >>>>>>>> available in recent official forum topics. >>>>>>>> >>>>>>>> >>>>>>>> 2011/5/17 Tristram Cheer<[email protected]> >>>>>>>> >>>>>>>> I think a real bug tracker would work the best to be honest >>>>>>>> >>>>>>>>> On 17 May 2011 18:16, Butch Evans<[email protected]> wrote: >>>>>>>>> >>>>>>>>> On Tue, 2011-05-17 at 16:41 +1200, Tristram Cheer wrote: >>>>>>>>> >>>>>>>>>> So there's been a bit of talk on the forums recently about the >>>>>>>>>>> >>>>>>>>>>> stablity >>>>>>>>>> >>>>>>>>> of >>>>>>>>> >>>>>>>>>> ROS 5 and as such the changelogs and known issues that MT don't >>>>>>>>>>> >>>>>>>>>>> release. >>>>>>>>>> When a client like ourselves identifies and issue like the SNMP >>>>>>>>>> memory >>>>>>>>>> >>>>>>>>> leak >>>>>>>>> >>>>>>>>>> today MT don't let everyone know and as a result quite a few >>>>>>>>>>> >>>>>>>>>>> people >>>>>>>>>> >>>>>>>>> are >>>>>>> >>>>>>>> left >>>>>>>>> >>>>>>>>>> with odd problems they can't explain (When was the last time you >>>>>>>>>>> >>>>>>>>>>> thought >>>>>>>>>> SNMP would be the cause of your major router crashing issue?) >>>>>>>>>> >>>>>>>>>>> So an Idea, Just like we have this list for MT talk outside of >>>>>>>>>>> >>>>>>>>>>> MT's >>>>>>>>>> >>>>>>>>> somewhat >>>>>>> >>>>>>>> twitchy delete finger forum why dont we start a bugtrack where >>>>>>>>>>> >>>>>>>>>>> everyone >>>>>>>>>> >>>>>>>>> can >>>>>>>>> >>>>>>>>>> submit problems and update us with what support tells them etc >>>>>>>>>>> >>>>>>>>>>> etc, >>>>>>>>>> >>>>>>>>> That >>>>>>> >>>>>>>> way >>>>>>>>>> >>>>>>>>>> we would have a resource we could turn to for open issues before >>>>>>>>>>> >>>>>>>>>>> we >>>>>>>>>> >>>>>>>>> start >>>>>>> >>>>>>>> down the path of contacting support? >>>>>>>>>> Do you want a real bugtracker, a forum, a wiki or something else? >>>>>>>>>> >>>>>>>>>> I'd >>>>>>>>> >>>>>>>> be happy to set up whatever you like. >>>>>>> >>>>>>>> -- >>>>>>>>>> >>>>>>>>>> ******************************************************************** >>>>>>>>>> * Butch Evans * Professional Network >>>>>>>>>> Consultation* >>>>>>>>>> * http://www.butchevans.com/ * Network Engineering >>>>>>>>>> >>>>>>>>>> * >>>>>>>>> >>>>>>>> * http://store.wispgear.net/ * Wired or Wireless Networks >>>>>>> >>>>>>>> * >>>>>>>>> >>>>>>>> * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! >>>>>>> >>>>>>>> * >>>>>>>>> >>>>>>>> * NOTE MY NEW NUMBER: 702-537-0979 * >>>>>>> >>>>>>>> ******************************************************************** >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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/20110517/f6aacd7c/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 >>>>>>>>> >>>>>>>>> -------------- next part -------------- >>>>>>>>> >>>>>>>> An HTML attachment was scrubbed... >>>>>>>> URL:< >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> http://www.butchevans.com/pipermail/mikrotik/attachments/20110517/0d0d88e5/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 >>>>>>>> >>>>>>>> -------------- next part -------------- >>>>>>>> >>>>>>> An HTML attachment was scrubbed... >>>>>>> URL:< >>>>>>> >>>>>>> >>>>>> http://www.butchevans.com/pipermail/mikrotik/attachments/20110517/40aff1c1/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 >>>>>> _______________________________________________ >>>>>> 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/20110518/944cb63e/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 >>>>> >>>>> _______________________________________________ >>>> 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/20110518/32652c42/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 >>> >>> _______________________________________________ >> 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/20110518/8d9d28af/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 _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
