Re: feedback on new wiki theme

Matthew East wrote: > Hi, > > Recently I've been developing a new theme which is intended to replace > the existing themes on the documentation wiki > (https://help.ubuntu.com/community). The intention of the theme is to > make reading the wiki easier for a user (so the interface should be > clean

Firefox stable release update testing

Hello! We will soon be pushing out updates to Firefox in three stable Ubuntu releases: Dapper, Edgy and Feisty and would appreciate help in testing the packages. The candidate packages can be found in the new Mozilla section of the QA website: https://mozilla.qa.stgraber.org/ Please test and

Re: Reporting bugs for unofficially support ports (powerpc in particular)?

Michael R. Head wrote: > I've been trying to report a bug about an app on the powerpc > architecture > ( https://bugs.launchpad.net/ubuntu/+source/gpar2/+bug/146606 ). > > It's been marked invalid because it occurs on powerpc, even after > assigning it to the PowerPC team. I'd still like to try and

Re: A responsible use of the "incomplete" status.

Sarah Hobbs wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > You know, it's mails like this that make me really feel that it's not > worth triaging bugs, or aiming for a reasonably decent QA. > > It's when you start dealing with ~1000 bugs over a few source packages > that this kind of

Re: TheOpenCD forks to OpenDisc

Conrad Knauer wrote: > http://ccg.id.au/blog/?p=88 > > ... and its Project Lead goes with it, leaving TheOpenCD in limbo. > Will this have any impact on Gutsy? Will future releases have the > Windows component based on OpenDisc or will Canonical attempt to > revive it? > We will not continue ac

Beta ISO testing: Updated test cases and reporting

Hi, In preparation for gutsy beta images the test cases have been updated and restructured. The tests are now grouped by a generic category, such as Live CD session, Live install and Server install. The wiki page for each procedure is short, but in turn links to distro-flavour-specific modules

Re: That need to close bugs?

Reinhard Tartler wrote: > Sarah Hobbs <[EMAIL PROTECTED]> writes: > > >> As one of those who triages various KDE bugs...in the area of KDEBase, >> in particular, there are around 450 open bugs, we *have* to close >> invalid bugs. There are around 750, with the INVALID and WONTFIX bugs >> includ

Re: USB Mass Storage not working in Gutsy -- release critical fix needed!(?)

Alex Jones wrote: > https://bugs.launchpad.net/ubuntu/+source/hal/+bug/136845 > > Something must be wrong in the upgrade path. Thanks for bringing this to the list. Henrik -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lis

Re: That need to close bugs?

Alexandre Strube wrote: > I want to raise something here... > > One of the things that made me take some distance from daily ubuntu > development was a raid of newer people which closes the bugs for > whatever reason. If the bug is not good enough for them, they close. > This is more or less an

Re: Important bug for Gutsy

Martin Olsson wrote: > Many laptops come with Vista pre-installed. It would be nice if Ubuntu > could be installed to dual-boot with such a Vista installation. > > Currently, there is this annoying bug which blocks resizing of Vista > NTFS partitions and this is making it very hard to install Ubu

Re: All-sides Testing Report of Ubuntu-7.04 from BSTQC

konghao wrote: > >> As I suggested last time, perhaps the Ubuntu BugSquad could organize a >> Bi-Annual Bug Blitz -- putting the BSTQC report on the Ubuntu wiki, and >> annotating it with links to the equivalent Launchpad bug reports. >> >> Perhaps so

Re: All-sides Testing Report of Ubuntu-7.04 from BSTQC

konghao wrote: >> konghao schrieb: >> >>> Release of All-sides Testing Report of Ubuntu-7.04 >>> > > >> Is this "pure" 7.04, or are updates taken from the ubuntu-security and/or >> ubuntu-updates repositories? >> > > I am not very clear about the meaning of "pure", if you mean

Tribe 2 ISO candidates available for testing

The first Tribe-2 candidates are now available for testing. You can find download links, md5 sums and report results on the ISO tracker: https://isotesting.stgraber.org Please help us find the nasty bugs early in the cycle so we can focus on polish closer to release :) For alpha releases we re

Re: Launchpad bug workflow change

Scott Kitterman wrote: > >> So far I think most will agree. It seems that the controversy centers >> around the restricted use of In Progress, Fix Committed and Fix >> Released. There is also a feeling that Todo and Triaged are superfluous. >> > > I can see the point in the new states.

Re: Launchpad bug workflow change

Hi all, Instead of answering each point made by each person I will try to explain the reasoning behind this change in a more structured way. The reality is that the development team is flooded with open bugs ATM and we need to take steps to improve this situation. We have over 30 000 open bugs

Re: Launchpad bug workflow change

Jordan Mantha wrote: >> >> If we want a certain group of people who write code but are not MOTU or >> core-dev to be able to set the whole range of status settings then we >> can set up a team that gives that access. I agree that people can write >> valuable code without doing .deb packaging for

Re: Launchpad bug workflow change

Scott Kitterman wrote: >>> >>> I have no idea. I think here you are taking them away for no good reason >>> that I have seen. >>> >> What has beene taken away? The ability for anyone with an email address >> to set bugs to In progress and similar. We have also added 3 new bug >> states whic

Re: Launchpad bug workflow change

Scott Kitterman wrote: > OK. I guess I missed the meeting. Where is this change documented? Was > there a spec? Anything those of us who were unable to participate in UDS > could have seen this coming? > The discussion was scheduled on a public webpage, but the Launchpad spec was not publ

Re: Launchpad bug workflow change

Jordan Mantha wrote: >>> >>> >> Please don't interpret it that way :) As I replied to Scott, if the bug >> is not handled by someone who can upload to Ubuntu then it's fair to say >> that nobody is working on a fix in Ubuntu. >> > > This is just not true. In Universe we have a grea

Re: Launchpad bug workflow change

Scott Kitterman wrote: >> >> I don't think you should assign a bug to yourself if you are not working >> on fixing it. IMO you should try to move it along to the Triaged state >> as efficiently as possible and bugs should be assigned to the developer >> or dev team who is going to fix it. >> >> I r

Re: Launchpad bug workflow change

Onno Benschop wrote: >>> >>> >> When you say 'a member of the general community' do you mean not in >> ubuntu-qa and not a developer (I ask because people from the volunteer >> community are also in those groups)? If you are not then it it's >> correct that you cannot set those state

Re: Launchpad bug workflow change

Scott Kitterman wrote: > On Tuesday 19 June 2007 17:59, Henrik Nilsen Omma wrote: > > >> If you are not a developer then it is misleading to set it to In >> Progress because nobody is actually working on the fix and it may never >> be fixed. >> > > U

Re: Launchpad bug workflow change

Phillip Susi wrote: > Henrik Nilsen Omma wrote: >> If you are not a developer then it is misleading to set it to In >> Progress because nobody is actually working on the fix and it may >> never be fixed. > > There are those of us who are not developers but do s

Re: Launchpad bug workflow change

Onno Benschop wrote: > On 20/06/07 04:56, Henrik Nilsen Omma wrote: > >> What I did not mention in my first mail (just confirmed this with the LP >> developer), is that the groups who can set the different states will now >> also change. >> >>

Re: Launchpad bug workflow change

Scott Kitterman wrote: > Will 'Won't Fix' bugs show up in default search results? I think it would > be good for them to show up to minimize duplicate submissions of things > that aren't going to get done. It's a closed state so I expect they won't (we'll find out tomorrow). It would be more u

Re: Launchpad bug workflow change

Phillip Susi wrote: > Henrik Nilsen Omma wrote: >> I agree that 'evaluating the urgency' should also fit into the >> Triaged state. However, not that this can only be done by ubuntu-qa >> or developers (setting importance). Assigning resources can really >>

Re: Launchpad bug workflow change

Phillip Susi wrote: > Henrik Nilsen Omma wrote: >> * Triaged will mean that a bug has all the information attached to >> it that a developer needs to fix it. The 'confirmed' state was >> previously used for this purpose, but many users were 'confirming'

Launchpad bug workflow change

Tomorrow (2007-06-20) the Launchpad team will update the bug tracker with a new set of bug states to help projects like Ubuntu improve bug management. The changes will allow for greater fine tuning of our bug management and the new labels should hopefully also make more sense to users. The fol

Call for Release Candidate testing (again)

After a heroic effort by the kernel team over the weekend the sata_nv kernel bugs that were haunting us are finally squashed. That leaves us a very small window for testing the Release Candidate images, so please help out if you can. The CD images to test are 20070415 and DVDs are 20070516. Ge

Re: Windows CD has wrong label

t u wrote: > Hi, > > I imagine that fixing this wouldn't take too long (I apologize if I'm > wrong). This is the bug report: https://launchpad.net/ubuntu/+bug/71119 > Fixed in my local branch. Will upload later this week with various other changes. Thanks for testing the WinFOSS section. Henr

Re: feedback and help for mousetweaks specification

Francesco Fumanti wrote: > Hello, > > > I would like to inform you about the mousetweaks specification > created by Henrik Nilsen Omma in launchpad. I fleshed it out in the > corresponding wiki page: > https://wiki.ubuntu.com/Accessibility/Specs/MouseTweaks?action=show >

Re: forum-ambassadors to improve communication between forum users and developers

Roald (ubuntu_demon) wrote: > Please read the entire document. All feedback is welcome. Especially > feedback regarding communication between us forum ambassadors and you > developers. For example in what way should we report to you about > interesting trends and wishes ? > I fear that many peo