[MeeGo-dev] bugs.meego.com 1h maintenance break 27.08.2010 @ 13.00 EEST
Hello MeeGo :) We need to have a short maintenance break on MeeGo Bugzilla instance, http://bugs.meego.com The purpose is to apply security patches and add missing libraries for graphical reports. Bugzilla will not be accessible during the maintenance break. We apologize for the inconvenience and the rather short notice. We estimate the break to last approx. 1 hour at most. The break starts on Friday 27th of August 2010 at 13.00 EEST Please propagate this information, thank you! Best regards, Eric Le Roux ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Review board for MeeGo
Hi, >-Original Message- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >On Behalf Of ext Andre Klapper >Sent: 15 September, 2010 13:26 >To: meego-dev@meego.com >Subject: Re: [MeeGo-dev] Review board for MeeGo > >Hej hej, > >Am Dienstag, den 14.09.2010, 09:28 +0300 schrieb Vitaly Repin: >> It works better that reviewboard especially for the bug fixes as the >> code review and bug are tracked in one tool which is much simpler than >> jumping between different tool. > I support Vitaly's view, integration is key. >https://wiki.mozilla.org/Auto-tools/Projects/BugzillaReviewImprovement >currently lists two options with their pros and cons: >ReviewBoard and Splinter. Thanks for the link Andre :) > >andre >-- >Andre Klapper (maemo.org bugmaster) > Cheers, Eric >___ >MeeGo-dev mailing list >MeeGo-dev@meego.com >http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] 15 min maintenance break on bugs.meego.com Saturday 18.09.2010 @ 13.00 EET!
Hi all, We need a short maintenance break to bring you more Featurezilla related enhancements. Highlights: - concurrent workflows for bugs and features on search and reports pages - statuses and resolutions are shown accordingly - Pick one or the other, or both at the same time - By default the workflow matches the classification you select The break happens on Saturday 18.09.2010 @ 13.00 EET Sorry for any inconvenience and (again!) the rather short notice. Please propagate this information, thank you! Best regards, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Virtual kbd & libmeegotouch now under OS Base
Hi, Virtual keyboard and libmeegotouch components, previously under Handset UX product, are now under OS Base product on bugs.meego.com. Best regards, Eric Le Roux MeeGo EM lead ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego Bugs Access Denied
Hi Gary, We are working on making these defects visible again as soon as possible. There's a chance that the number still grows in the coming days yet the situation should come back to normal quite soon. Sorry for the inconvenience! BR, Eric >-Original Message- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >On Behalf Of ext Gary Birkett >Sent: 28 October, 2010 12:29 >To: Development for the MeeGo Project >Subject: [MeeGo-dev] Meego Bugs Access Denied > >Hey, > >I have encountered a number of bugs this morning as part of my work on >the meego bug tracker which are giving an error: >"You are not authorized to access bug #[bugid]" >(related to something I expected to read and digest) > >This issue effects people in other areas too > >A specific example this morning was stskeeps could not access >http://bugs.meego.com/show_bug.cgi?id=8474 > >this bug is highlighted multiple times in the acceptance report >http://wiki.meego.com/Quality/HandsetTestReport/1.2_N900Acceptance201010 >28 > >Is there a general documented mechanism to follow to get access to >these bugs or to generally unlock them? >(going through team leaders based on requirements is normal) > >Gary >___ >MeeGo-dev mailing list >MeeGo-dev@meego.com >http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego Bugs Access Denied
Hi, >-Original Message- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >On Behalf Of ext Thiago Macieira >Sent: 28 October, 2010 16:18 >To: meego-dev@meego.com >Subject: Re: [MeeGo-dev] Meego Bugs Access Denied > >On Thursday, 28 de October de 2010 05:44:09 Bradley Smith wrote: >> You need to be presenting a darn good reason why bugs are not being >> shown to everyone. > >Usually that reason is "security issue" or "customer sensitive >information". > This seems to fall under the "csi" category probably. >But like you said, there should be a way to request access for people >who need to know. > As far as I can tell, this situation is exceptional and we should return to normal very soon. I completely understand the frustration and actually share it... >-- >Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org > Senior Product Manager - Nokia, Qt Development Frameworks > PGP/GPG: 0x6EF45358; fingerprint: > E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 Cheers, Eric Le Roux MeeGo error management lead ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Approved feature number(was Re: 9241: New package Trunk:Testing/u-boot)
Hi Menon, >-Original Message- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >On Behalf Of ext Nishanth Menon >Sent: 05 November, 2010 15:58 >To: Nanjappa Madhusudhan.3 (EXT-Wipro/Helsinki) >Cc: meego-dev@meego.com; meego-packag...@meego.com; meego- >comm...@meego.com >Subject: [MeeGo-dev] Approved feature number(was Re: 9241: New package >Trunk:Testing/u-boot) > >ext-madhusudhan.3.nanja...@nokia.com wrote, on 11/05/2010 09:39 AM: >> You could start from here.. >> >> >http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Core%20OS%20Features >> >> The feature request gets assigned to the Core product manager, who >then will make a decision.. >> >+ MeeGo-dev, changing subject as well. > >http://meego.com/about/contribution-guidelines - the nice lil pic >does'nt point me to this Bureaucracy ;) > >http://wiki.meego.com/Contributing_to_MeeGo Does'nt tell me to file a >bugzilla. > >in fact if the MeeGo has some internal process, why should I(as a >community member) be forced through this process? > >infact googling for "approved feature number" in google on the site >meego.com does not return anything - why are we making the life of a >community contributor difficult? > Nobody's trying to make your life difficult ;) You're not looking into the right place I reckon. Here's the process: http://meego.com/developers/requirements I believe more detailed information is coming soon about it... >http://www.google.com/search?q=approved+feature+number+site%3Ameego.com&; >hl=en&num=10&lr=&ft=i&cr=&safe=images#sclient=psy&hl=en&lr=&source=hp&q= >%22approved+feature+number%22+site:meego.com&aq=f&aqi=&aql=&oq=&gs_rfai= >&pbx=1&fp=f436bf9c73b5ce9d > > >PS: for the meego-dev folks, thread of the discussion: >http://lists.meego.com/pipermail/meego-packaging/2010- >November/245770.html >-- >Regards, >Nishanth Menon Cheers, Eric Le Roux MeeGo error management lead >___ >MeeGo-dev mailing list >MeeGo-dev@meego.com >http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] N900 Developer Edition Release Blockers Flag
Hello MeeGons! A quick note to inform you that we just enabled a new flag in order to track the blockers related to the N900 DE release. This new flag can be proposed by any user with editbug credentials. Remember to clearly state in a bug comment the reasons why you propose it as blocker. In order to search for the flag, please use the Advanced Searching Using Boolean Charts at the bottom of the search/report bugzilla page. MeeGo_N900DE_Release_Blocker? Will show the proposed flags MeeGo_N900DE_Release_Blocker+ Will show the approved flagged bugs MeeGo_N900DE_Release_Blocker- Will show the rejected ones Approval or refusal is handled by Jukka Eklund. More people will be added in the flag granting group as we proceed. Iekku Huttunen acts as official EM for this exercise. Note that the "N900_Developer_Edition_Blocker" keyword is deprecated and has been removed. Happy bug hunting and fixing! Best regards, Eric Le Roux MeeGo EM Lead ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Meego Bugs Access Denied
Hi, On 3/31/11 12:05 AM, "ext Andre Klapper" wrote: >On Wed, 2011-03-30 at 15:56 -0500, Gabriel M. Beddingfield wrote: >> Currently, when someone happens upon a restricted bug, they >> get a scary red web page that shouts something like "Access >> Restricted! You are not authorized to view this bug." That >> page makes a person feel like they're an intruder, and are >> about to be escorted out of the building. >> >> Could this perhaps be toned down a little? Maybe add a link >> to this wiki page? +1 > >Feel free to file a request in bugs.meego.com against Bugzilla. Indeed, file a request so we make the warning more user friendly, thanks. > >andre >-- >Andre Klapper (maemo.org bugmaster) >http://www.openismus.com Cheers, Eric Le Roux MeeGo EM Lead > >___ >MeeGo-dev mailing list >MeeGo-dev@meego.com >http://lists.meego.com/listinfo/meego-dev >http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Meego Bugs Access Denied
Hi Marius, On 3/31/11 10:07 AM, "Marius Vollmer" wrote: >"ext eric.le-r...@nokia.com" writes: > >> Indeed, file a request so we make the warning more user friendly, >> thanks. > >Can't you just do it without having a request filed? Nope. As we have a distributed team to handle bugzilla it's way easier if we actually have a formal request... So it doesn't go into limbo if I or someone else don't do it immediately. Sorry for being _that_ demanding :P Cheers, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product "MeeGo Distribution Packages" has been created.
Hi, On 6/29/11 11:33 AM, "ext Zhao, Fan" wrote: >> Wednesday, June 29, 2011 4:15 PM >> Marius Vollmer wrote: >> >> "ext Zhao, Fan" writes: >> >> >> Wednesday, June 29, 2011 3:13 PM >> >> Marius Vollmer wrote: >> >> >> >> "ext Zhao, Fan" writes: >> >> >> >> > The purpose of the "MeeGo Distribution Packages" product is to >>provide >> >> > an option for people to report/triage bugs to packages, and it's >>setup >> >> > for 1.3 bug reporting at this moment. >> >> >> >> Creating a new product is nice, but it is different from moving >>existing >> >> bugs into it en masse. This mass moving was not announced, as far >>as I >> >> can see. It is impolite to massively move bugs around without >> >> cooperating with the 'owners' of those bugs. >> >> >> >> Or maybe I misunderstand. In any case, the direction is right, so >>maybe >> >> we can live with some bumps on the way. >> > >> > Mass movement of bugs is not expected at this moment. >> >> So why is Michael saying the following then: >> >> I wondered why bugs for our component, the virtual keyboard, were >> moved to newly created components without prior announcement, nor >> explanations. >> >> Here is an example of a bug that was moved without a comment: >> >> https://bugs.meego.com/show_activity.cgi?id=15554 >> >> Anyway, none of my business, so I shut up. :) > >I just did a search, around 15 VKB bugs were moved to the new product, so >I don't think it's mass movement. If there are problems for that >component, let's solve the specific problem, but let's not overshade the >general direction. The point here isn't about the administrative task of moving bugs with the "change several bugs at once" bugzilla feature but making sure that an appropriate comment is attached to the bugs. So I guess you could remind anyone on your side involved into moving the bugs that it's mandatory to at least put a comment with the reasoning behind the action. In this case, yanshuang.zh...@intel.com needs to be reminded. Doing so will generate an email notification to anyone having incentive on the bug. Of course, announcements on the ML are good but as we all know, it's simply not enough as Michael and Marius point out... > >Thanks for bringing it up anyway. Another point is that one could actually challenge why some bugs were moved there if the purpose is to monitor 1.3 release. IMHO anything done already doesn't need to move, does it? Just verified and closed is largely enough. > >Thanks, >Fan Cheers, Eric >___ >MeeGo-dev mailing list >MeeGo-dev@meego.com >http://lists.meego.com/listinfo/meego-dev >http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product "MeeGo Distribution Packages" has been created.
Hi Arjan, On 6/29/11 4:41 PM, "ext Arjan van de Ven" wrote: >On 6/29/2011 2:05 AM, eric.le-r...@nokia.com wrote: >> So I guess you could remind anyone on your side involved into moving the >> bugs that it's mandatory to at least put a comment with the reasoning >> behind the action. > >so as a user of bugzilla I strongly disagree with your statement. >I use the "filter bug mail" feature so that I only get bugmail on >important events (real new information added, not just noisy bookkeeping >things) >that feature gets completely and utterly destroyed if the QA person, in >addition to the actual change, also puts in "I changed this" as comment. >(and that comment adds absolutely zero value) I hear you but isn't moving a bug to another component an important enough event it's worth recording it in an inline comment on the bug? I agree some of the QA activities may not bring added value to the report itself and if too many alter the readability but I think moving bugs deserves clear documentation e.g. Why someone makes decision to move it... BR, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product "MeeGo Distribution Packages" has been created.
Hi Arjan, On 6/30/11 4:41 PM, "ext Arjan van de Ven" wrote: >On 6/29/2011 11:57 PM, eric.le-r...@nokia.com wrote: >> >> I hear you but isn't moving a bug to another component an important >>enough >> event it's worth recording it in an inline comment on the bug? > >I would say not. the component is metadata and does not add value to the >bug itself >it doesn't help in any way shape or form in getting it fixed. > >I have a very simple idea on bugs; the value of a bug lies in its >ability to fix something in the OS >that makes the OS better. Anything else around the bug is either neutral >or overhead. > >it's not just about the readability of the bug itself (which is >important); it is about the readability >of my, and every developers, bugzilla email folder. If the >signal-to-noise ratio of that folder is not >high enough, I'm sorry but it will get ignored. > > >Changing some bits in a database, which are just bits on a spinning >piece of rust, that has the effect >of changing components does not add value in any way, shape or form in >my definition of bug value above... >... and thus is "noise" in the bug mail folder. Now that you put it this way, I'm more than convinced that nothing but value should matter in bug reports though I'm a bit skeptical on what it actually means for other target population than developers. Hopefully, QA and other average users won't contribute too much to what can be perceived as noise with their activities, questions ,etc... Cheers, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] MeeGo bugzilla on gitorious
Hi everyone! I'm very happy to announce that we have finally released our MeeGo bugzilla instance code on gitorious. Check it out here: https://gitorious.org/meego-bugzilla A few adjustments are still needed in order to get in full sync with the production environment. Shuang Wan from Intel now takes the lead to maintain the repository. Both Stephen and I are stepping back though we will remain around on needed basis. I would like to thank Stephen for the tremendous and quality work he's been delivering and his extremely valuable contribution to the MeeGo project. A clear direction was given and a great vision of collaborative work. I'm sure Shuang will take this legacy further and get contributions from you, developers, in order to make MeeGo bugzilla a reference in usability and a wonderful environment to work in. I would like to emphasize that one of the next big step is probably an upgrade to the latest stable bugzilla 4.0.x branch which comes with noticeable improvements. Again, Shuang will lead and provide a graceful deployment roadmap as defined by Stephen. Of course, one of the key reason to openly maintain our code is not only about giving full visibility to Meego community but to gain traction and get more people involved. I really would like to encourage you to collaborate, submit ideas and patches and make Meego bugzilla really yours. Discussions are best initiated on the meego-qa ML where you will find Andre, Iekku, Fan and many others to support your requests and gets things moving on. Thanks for your attention and have a great summer :) Cheers, Eric Le Roux MeeGo EM Lead ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo bugzilla on gitorious
Hi Dave, On 7/4/11 3:25 PM, "ext Dave Neary" wrote: >Hi, > >eric.le-r...@nokia.com wrote: >> I'm very happy to announce that we have finally released our MeeGo >> bugzilla instance code on gitorious. >> Check it out here: https://gitorious.org/meego-bugzilla > > > >> I would like to thank Stephen for the tremendous and quality work he's >> been delivering and his extremely valuable contribution to the MeeGo >> project. >> A clear direction was given and a great vision of collaborative work. >> I'm sure Shuang will take this legacy further and get contributions from >> you, developers, in order to make MeeGo bugzilla a reference in >> usability and a wonderful environment to work in. > >I just wanted to say thanks and congratulations! This is going to be >useful whenever we see Bugzilla related bugs/feature requests. Thanks for your encouragement :) Indeed, I truly believe this is a great enabler and we get actual contributions. > >> I really would like to encourage you to collaborate, submit ideas and >> patches and make Meego bugzilla really yours. > >Do you have a list of bugs which require Bugzilla modifications handy, >by any chance? This is just my personal list, https://bugs.meego.com/buglist.cgi?quicksearch=19714%2C10540%2C10251%2C3187 The most important item so far is https://bugs.meego.com/show_bug.cgi?id=3187 as it's almost mandatory to allow graceful tracking accross multiple hardware/releases Note we had a custom version but it was dismissed as it doesn't scale up in MeeGo context. I see more viability in focusing on the upstream patch, make it solid and contribute back... > >Cheers, >Dave. > >-- >Email: dne...@maemo.org >Jabber: bo...@jabber.org Best regards, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo bugzilla on gitorious
Hi Auke, On 7/4/11 8:19 PM, "ext Kok, Auke-jan H" wrote: >On Mon, Jul 4, 2011 at 4:51 AM, wrote: >> Hi everyone! >> I'm very happy to announce that we have finally released our MeeGo >>bugzilla >> instance code on gitorious. >> Check it out here: https://gitorious.org/meego-bugzilla > >Can I ask why this isn't hosted under meego.gitorious.org instead? Good point. I'll make a request so we can move the repo there... > >Auke Cheers, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo bugzilla on gitorious
Hi again, On 7/5/11 10:50 AM, "Le-Roux Eric (Nokia-MS/Helsinki)" wrote: >Hi Auke, > >On 7/4/11 8:19 PM, "ext Kok, Auke-jan H" wrote: > >>On Mon, Jul 4, 2011 at 4:51 AM, wrote: >>> Hi everyone! >>> I'm very happy to announce that we have finally released our MeeGo >>>bugzilla >>> instance code on gitorious. >>> Check it out here: https://gitorious.org/meego-bugzilla >> >>Can I ask why this isn't hosted under meego.gitorious.org instead? > >Good point. I'll make a request so we can move the repo there... Here's the ticket: https://bugs.meego.com/show_bug.cgi?id=20620 Thanks in advance Mike ;) >> >>Auke > >Cheers, >Eric Cheers, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
