On Mon, Jul 07, 2008 at 12:10:45PM +0300, Rakotomandimby Mihamina wrote:
Matt Zimmerman wrote:
If you were unaware that this was going on, perhaps we could do a better job
of communicating this type of effort with the public.
I would suggest a kind of summary of bugs (and their progression)
On Tue, Jul 15, 2008 at 09:16:04AM +0100, Matt Zimmerman wrote:
On Mon, Jul 07, 2008 at 12:10:45PM +0300, Rakotomandimby Mihamina wrote:
Matt Zimmerman wrote:
If you were unaware that this was going on, perhaps we could do a better
job
of communicating this type of effort with the
2008/7/11 Matthew Paul Thomas [EMAIL PROTECTED]:
That doesn't require a script. For example, bugs targeted to
intrepid-alpha-2, sorted by number of duplicates:
https://bugs.edge.launchpad.net/ubuntu/+bugs?orderby=-number_of_duplicatesfield.milestone%3Alist=1320
Cool, didn't know that! Added to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryce Harrington wrote on 07/07/08 21:55:
On Mon, Jul 07, 2008 at 10:52:44PM +0300, Timo Jyrinki wrote:
...
I think the single most needed feature in Launchpad regarding this
would be the possibility for voting, as done in bugzilla.
I don't
Voting could also reduce noise from me too! comments. (On the other
hand, there's the risk that the reduction in me too! comments might be
outweighed by the increase in this bug has X votes, why hasn't it been
fixed? comments.)
Sometimes useful information gets buried among tons of me too
The first step is maybe to start taking in much higher account users
contributions. My experience is that patches can stay in launchpad for
months and in those cases it is entirely up to who contributed those to
bother people until they ack a fix. I am not talking about my often
blind
Olá Oliver e a todos.
On Monday 07 July 2008 12:50:19 Oliver Grawert wrote:
Am Montag, den 07.07.2008, 12:42 +0100 schrieb (``-_-´´) -- Fernando:
* the manual way, rename the source.list hardy mentions to intrepid and do
an apt-get dist-update;
you know that this is highly discouraged
Olá Markus e a todos.
On Monday 07 July 2008 13:08:34 Markus Hitter wrote:
You confirm my point, thanks. I knew this myself already, but how do
you get this out to the thousands of potential beta testers?
MarKus
As I said, those you have the resources (extra PC, virtual OS, etc) and the
2008/7/7 Bryce Harrington [EMAIL PROTECTED]:
I think the single most needed feature in Launchpad regarding this
would be the possibility for voting, as done in bugzilla.
I don't know if I necessarily agree with this. Voting may feel good
from a user perspective and certainly couldn't hurt,
2008/7/7 Evan [EMAIL PROTECTED]:
I started a discussion on the dev cycle on this list a while back
Yes, I remember that discussion. I think those ideas you had were good, it
was a bit of a pity that they were not implemented into the release process.
Hopefully things will change for the next
Am Montag, den 07.07.2008, 09:33 +0100 schrieb Matt Zimmerman:
On Sun, Jul 06, 2008 at 03:27:46PM -0400, Scott Kitterman wrote:
Do we need to reconsider how we approach getting to a release? For an LTS
release should we just add 2 months on the schedule? It was done
officially for Dapper
Am 07.07.2008 um 11:06 schrieb Sebastian Breier:
The problem is that even with all the alpha/beta/rc testing
available to
Ubuntu, the most tests are only done when the release is out.
Yes, a lot of alpha-beta-sonstewas Releases are usually available,
but also yes, they are well hidden
Olá Markus e a todos.
On Monday 07 July 2008 12:18:27 Markus Hitter wrote:
Right now I tried to find downloads and/or upgrade instructions for
the next release, but it's almost impossible to find them beginning
at the main site. There is a menu Community - Get Involved, but no
mention
On Monday 07 July 2008 08:50, Cory K. wrote:
Scott Kitterman wrote:
I think the only path to better tested releases is higher quality test
releases.
Sad fact is people don't install the alpha/betas at the same level as
final. So more actual testing/feedback was done after release. I can
On Mon, Jul 07, 2008 at 08:30:28AM -0400, Scott Kitterman wrote:
This is not sustainable in the long term. Before long people will be
saying, Everyone know not to upgrade Ubuntu until the first point
release. Then we don't get the end user base to test until .1 and we have
to bugfix from
Hi,
On Monday 07 July 2008 15:12:13 Scott Kitterman wrote:
[..]
I suspect that we may be in a similar position with Ubuntu. We need to
radically rethink testing and how test results get back into fixes. I
believe that Ubuntu has gotten more complex and we need to match our
test/fix
Am Montag, den 07.07.2008, 14:04 +0100 schrieb Matt Zimmerman:
On Mon, Jul 07, 2008 at 08:30:28AM -0400, Scott Kitterman wrote:
This is not sustainable in the long term. Before long people will be
saying, Everyone know not to upgrade Ubuntu until the first point
release. Then we don't
On Mon, Jul 7, 2008 at 5:06 AM, Sebastian Breier
[EMAIL PROTECTED] wrote:
The problem is that even with all the alpha/beta/rc testing available to
Ubuntu, the most tests are only done when the release is out.
There's also no chance whatsoever that the subset of users that
beta-test, even if
On Mon, Jul 7, 2008 at 7:50 AM, Oliver Grawert [EMAIL PROTECTED] wrote:
hi,
Am Montag, den 07.07.2008, 12:42 +0100 schrieb (``-_-´´) -- Fernando:
* the manual way, rename the source.list hardy mentions to intrepid and do
an apt-get dist-update;
you know that this is highly discouraged since
On Mon, Jul 7, 2008 at 10:00 AM, Sebastian Breier
[EMAIL PROTECTED] wrote:
It's not that I don't want to test the alphas, it's the fear that I
might not be able to do my work tomorrow.
And separate alpha installs just don't do the testing job. ;)
This is true. I tried to dual boot Edgy when
On 2008/07/07 13:18 (GMT+0200) Markus Hitter apparently typed:
Yes, a lot of alpha-beta-sonstewas Releases are usually available,
but also yes, they are well hidden from the interested person.
FWIW, and I know nothing I say here is likely to change anything, but I
consider Launchpad a
Am 07.07.2008 um 15:12 schrieb Scott Kitterman:
There was some discussion at UDS about developing the ability to
trivially
clone a host machine into a VM so that users could easily test
their setups.
You can do this already. On the host machine, set aside a spare
partition for the OS,
Mackenzie Morgan wrote:
Oliver Grawert wrote:
(``-_-´´) -- Fernando wrote:
* the manual way, rename the source.list hardy mentions to intrepid and do
an apt-get dist-update;
you know that this is highly discouraged since it wont catch teh special
cases update-manager has functions for ?
On Mon, Jul 7, 2008 at 10:53 AM, Emmet Hikory [EMAIL PROTECTED] wrote:
Mackenzie Morgan wrote:
Oliver Grawert wrote:
(``-_-´´) -- Fernando wrote:
* the manual way, rename the source.list hardy mentions to intrepid and do
an apt-get dist-update;
you know that this is highly discouraged
2008/7/7 Scott Kitterman [EMAIL PROTECTED]:
On Monday 07 July 2008 08:50, Cory K. wrote:
Sad fact is people don't install the alpha/betas at the same level as
final. So more actual testing/feedback was done after release. I can
tell you for sure this was the case for Ubuntu Studio.
For
Scott Kitterman wrote:
I think the only path to better tested releases is higher quality test
releases.
and later
Personally, I think it means we need to be doing a much better job of testing
and bug fixing as developers.
...
The moral of the story is that my project had increased in
On Monday 07 July 2008 09:04, Matt Zimmerman wrote:
On Mon, Jul 07, 2008 at 08:30:28AM -0400, Scott Kitterman wrote:
This is not sustainable in the long term. Before long people will be
saying, Everyone know not to upgrade Ubuntu until the first point
release. Then we don't get the end
http://ubuntuforums.org/showthread.php?t=769112
NOW people realize that something is wrong with the dev cycle!
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
On Mon, Jul 7, 2008 at 11:43 AM, Luke L [EMAIL PROTECTED] wrote:
http://ubuntuforums.org/showthread.php?t=769112
NOW people realize that something is wrong with the dev cycle!
I started a discussion on the dev cycle on this list a while back
Mackenzie Morgan [2008-07-07 12:26 -0400]:
The one thing I would like to point out regarding PA is that there
isn't anyone in charge of sound in Ubuntu anymore. After Daniel Chen
stepped down after Feisty, nobody else took over.
Luke Yelavich is taking over audio infrastructure maintenance.
On Mon, Jul 7, 2008 at 12:48 PM, Martin Pitt [EMAIL PROTECTED] wrote:
Mackenzie Morgan [2008-07-07 12:26 -0400]:
The one thing I would like to point out regarding PA is that there
isn't anyone in charge of sound in Ubuntu anymore. After Daniel Chen
stepped down after Feisty, nobody else took
Oliver Grawert pisze:
hi,
Am Montag, den 07.07.2008, 12:42 +0100 schrieb (``-_-´´) -- Fernando:
* the manual way, rename the source.list hardy mentions to intrepid and do an
apt-get dist-update;
you know that this is highly discouraged since it wont catch teh special
cases update-manager has
On Mon, 07 Jul 2008, Emmet Hikory wrote:
This isn't a CLI vs. GUI issue, it's that some upgrade cases don't
work well for special reasons. Some of these are difficult to encode
in terms of provides, conflicts, and replaces, and some are even
impossible. Upgrade Manager (which also has a
On Mon, Jul 07, 2008 at 01:57:26PM -0400, Daniel Robitaille wrote:
On Mon, 07 Jul 2008, Emmet Hikory wrote:
This isn't a CLI vs. GUI issue, it's that some upgrade cases don't
work well for special reasons. Some of these are difficult to encode
in terms of provides, conflicts, and
On Mon, Jul 7, 2008 at 2:01 PM, Mathias Gug [EMAIL PROTECTED] wrote:
On Mon, Jul 07, 2008 at 01:57:26PM -0400, Daniel Robitaille wrote:
On Mon, 07 Jul 2008, Emmet Hikory wrote:
This isn't a CLI vs. GUI issue, it's that some upgrade cases don't
work well for special reasons. Some of
On Mon, Jul 7, 2008 at 2:07 PM, Mackenzie Morgan [EMAIL PROTECTED] wrote:
On Mon, Jul 7, 2008 at 2:01 PM, Mathias Gug [EMAIL PROTECTED] wrote:
On Mon, Jul 07, 2008 at 01:57:26PM -0400, Daniel Robitaille wrote:
On Mon, 07 Jul 2008, Emmet Hikory wrote:
This isn't a CLI vs. GUI issue, it's
On Mon, 7 Jul 2008 13:57:26 -0400 Daniel Robitaille [EMAIL PROTECTED]
wrote:
update-manager has a cli client? Never heard of it. How do you call it?
sudo do-release-upgrade
Scott K
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
On Mon, 07 Jul 2008, Scott Kitterman wrote:
On Mon, 7 Jul 2008 13:57:26 -0400 Daniel Robitaille [EMAIL PROTECTED]
wrote:
update-manager has a cli client? Never heard of it. How do you call it?
sudo do-release-upgrade
+1 for the availability of that command
-1 for it's name. Even
On Monday 07 July 2008 14:07, Mackenzie Morgan wrote:
On Mon, Jul 7, 2008 at 2:01 PM, Mathias Gug [EMAIL PROTECTED] wrote:
On Mon, Jul 07, 2008 at 01:57:26PM -0400, Daniel Robitaille wrote:
On Mon, 07 Jul 2008, Emmet Hikory wrote:
This isn't a CLI vs. GUI issue, it's that some upgrade
hi,
Am Montag, den 07.07.2008, 19:42 +0200 schrieb Przemysław Kulczycki:
Oliver Grawert pisze:
hi,
Am Montag, den 07.07.2008, 12:42 +0100 schrieb (``-_-´´) -- Fernando:
* the manual way, rename the source.list hardy mentions to intrepid and do
an apt-get dist-update;
you know that
2008/7/7 Emmet Hikory [EMAIL PROTECTED]:
While we all tend to be busy much of the time, perhaps there are ways
that we can improve the view of bugs in need of attention, or
otherwise help understand which bugs are likely to be perceived as
painful to users at release time.
I think the single
On Tue, Jul 08, 2008 at 12:25:40AM +0900, Emmet Hikory wrote:
Scott Kitterman wrote:
Setting up an automatic install / upgrade / remove / purge tester
would be good, perhaps using piuparts or similar infrastructure,
although this requires considerable resources in terms of local
storage
On Mon, Jul 07, 2008 at 10:52:44PM +0300, Timo Jyrinki wrote:
2008/7/7 Emmet Hikory [EMAIL PROTECTED]:
While we all tend to be busy much of the time, perhaps there are ways
that we can improve the view of bugs in need of attention, or
otherwise help understand which bugs are likely to be
Scott Kitterman wrote:
On Monday 07 July 2008 08:50, Cory K. wrote:
Scott Kitterman wrote:
I think the only path to better tested releases is higher quality test
releases.
Sad fact is people don't install the alpha/betas at the same level as
final. So more actual testing/feedback was done
44 matches
Mail list logo
