Hi, On Thu, Sep 23, 2010 at 4:52 PM, Robin Burchell <[email protected]>wrote:
> Hi, > > On Thu, Sep 23, 2010 at 4:38 PM, Carsten Munk <[email protected]> wrote: > > 2010/9/23 Andre Klapper <[email protected]>: > > > Am Donnerstag, den 23.09.2010, 06:26 -0700 schrieb Michael Leibowitz: > > >> What are all these NB# bugs. I can't see them. I don't see any > BMC#'s. > > >> Does this release only fix bugs that I can't see and don't know about? > > > > > > NB is Nokia's internal non-public bugtracker. > > > > > > > Next question is why this is the only bugtracker mentioned in > > changelog for lib'meego'touch? Aren't bugs for projects part of the > > MeeGo project supposed to be in bugs.meego.com? > > This was precisely my line of thought, and the reason behind my filing > http://bugs.meego.com/show_bug.cgi?id=4900 (complete with some > interesting statistics of the time). > > It's a bit sad, in a way, that after all these years, we're still not > over the Maemo hurdles (https://bugs.maemo.org/show_bug.cgi?id=630) - > as pointed out recently by: > > http://yerga.wordpress.com/2010/09/11/nb666-my-eyes-hurt-about-nokia-internal-bugtracker/ > > On the bright side, since I filed that report, there has been some > marginal improvement in that there are occasionally MeeGo bugs in the > changelogs, but I'd still not call it a good situation - especially > given that the report itself has basically been ignored by those it > concerns, as far as I can tell. > > I think, at the end of the day, it boils down to a key point: Is this > an openly developed project, or a Nokia project? I don't think it's > too much to ask that bugs without commercially sensitive information > be filed on the public bugtracker specifically for that project, so > that developers - both with different affiliations (i.e. Intel) and > independent developers can try test/fix/generally help out. > Good points, but depends what you consider "commercially sensitive information", I bet some of these bugs have cores, logs and all kind of information that can easily leak device specs and other informations that can be considered sensitive. At the moment I can't see a good solution to solve this problem and agree that this should be completely open, but having two bugtracker is far from a optimal solution IMHO. Best regards, -- Valério Valério http://www.valeriovalerio.org > > > > Best regards, > > Carsten Munk > > -- > Robin Burchell > http://rburchell.com > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
