Hi Andre, Sorry for late reply.
> > If we could deploy bugzilla 4.x in near future, there will be an audit > > log there, and I believe it will record the key information there. > > We need to focus on the key changes to Bugzilla have the ticket filed > > and open discussed, for other trivial things, I don't think these > > could be followed as you enforced. > > For how requests send to Bugzilla admins, the channels could be in f2f > > discussion, phone call, IM, email... These will add more extra efforts > > to Bugzilla admins if everything discussed must have a bug entry in > > record. > > Does not need to be a bug entry always - a public mailing list is also > fine. ;-) > > F2F, phone call, IM, private email is fine for small issues (like adding > a component). > I don't think it's fine for bigger stuff (new products, adding some > fields to the Bugzilla UI, etc) if you don't want people to question > decisions, especially if others (e.g. members of EM team) disagree and > only find out after implementation... +1 Yes, agree one this. Product structure will impact more on bug reporting usability. So it's needed to have a bug entry for tracking and deployment needs to be agreed before take actions. So if no more open here, let's remove the *DRAFT STATUS* from wiki page? http://wiki.meego.com/Quality/MeeGoBugzillaRequestProcess > > Has happened too often in the past. > We've already discussed missing transparency before on this list. > > andre > -- > Andre Klapper (maemo.org bugmaster) > http://www.openismus.com Thanks Shuang _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
