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'
bugs when observed by a second person.
I
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
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 still work on
fixing bugs ;)
Non
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.
Um, non-developers work on fixes all the time. I did
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 states. This
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 realise that
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 great number of
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 public
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 which I think will be
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 example.
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 that the
original
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 Ubuntu
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
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:
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
included.
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
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 active
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 stuff
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 get
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
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
cleaner)
21 matches
Mail list logo
