Hi Frederic!
ext Frederic Crozat wrote:
> I'm going to play the devil advocate *on purpose*
I'll keep trying to answer the best I know and can.
> (I'm only commenting regarding Diablo release, not hardware release)
And I'm commenting about the release process in general, not the Diablo
release
Am Donnerstag, den 05.06.2008, 10:54 +0200 schrieb Luca Olivetti:
> It's useful to know that a bug is fixed, what isn't useful is that the
> fix isn't actually available
Quim already answered this partially, let me also try to describe our
bugmaster's point of view here.
We could create new
[an off-topic posting about fixed release dates.
please stop reading if not interested.]
Am Freitag, den 06.06.2008, 19:48 +0200 schrieb Krischan Keitsch:
> Quality first! Releasing shouldn't _only_ be a management decision. When the
> quality is as expected then the (scrum ?) team should hand ov
Am Samstag, 7. Juni 2008 schrieben Sie:
> ...
> > Quality first! Releasing shouldn't _only_ be a management
> > decision. When the quality is as expected then the (scrum ?)
> > team should hand over the responsibility to the management.
> > They can then powerpoint the great event ;-)
>
> And this
On Sun, Jun 8, 2008 at 3:58 PM, Luca Olivetti <[EMAIL PROTECTED]> wrote:
> En/na Frederic Crozat ha escrit:
>
>>
>> Translation : images are ready (and have probably been ready for some
>> time) and are held back for "media coverage" purpose.
>
> I wouldn't be so sure: packages in
> http://catalogu
En/na Frederic Crozat ha escrit:
>
> Translation : images are ready (and have probably been ready for some
> time) and are held back for "media coverage" purpose.
I wouldn't be so sure: packages in
http://catalogue.tableteer.nokia.com/updates/diablo/ are being updated
(or so it seems looking a
On Sat, Jun 7, 2008 at 11:16 PM, <[EMAIL PROTECTED]> wrote:
> Hi,
Hi,
I'm going to play the devil advocate *on purpose*, even if I know
perfectly what constraints exist
to release free software, both as a member of GNOME release team and a
Mandriva employee working on Mandriva Linux distribution
Hi,
> Am Donnerstag, 5. Juni 2008 schrieb [EMAIL PROTECTED]:
>> Frederic Crozat wrote:
>> > Remember that most people are not used to Nokia policy to embargo
>> > any date (even estimate) regarding software (or hardware) release.
True. These people need to understand that Nokia is a company watc
Am Freitag, 6. Juni 2008 schrieben Sie:
> Hi,
>
> Krischan Keitsch wrote:
> > Quality first! Releasing shouldn't _only_ be a management decision. When
> > the quality is as expected then the (scrum ?) team should hand over the
> > responsibility to the management. They can then powerpoint the great
Hi,
Krischan Keitsch wrote:
> Quality first! Releasing shouldn't _only_ be a management decision. When the
> quality is as expected then the (scrum ?) team should hand over the
> responsibility to the management. They can then powerpoint the great
> event ;-)
> Personally I consider fix release
Am Donnerstag, 5. Juni 2008 schrieb [EMAIL PROTECTED]:
> Frederic Crozat wrote:
> > Remember that most people are not used to Nokia policy to embargo any
> > date (even estimate) regarding software (or hardware) release.
>
> For simplicity's sake, I don't know when Diablo will be released.
Quality
On Thu, Jun 5, 2008 at 3:32 PM, <[EMAIL PROTECTED]> wrote:
> Marius Gedminas wrote:
>> Personally, I'm disappointed that when a bug is closed as "fixed in
>> diablo", as a user I've no idea how to get the updated package on my
>> N810.
>
> Please excuse my disbelief ... you guys are the strangest
Hi Josh,
[EMAIL PROTECTED] wrote:
> Please excuse my disbelief ... you guys are the strangest "users" I've
> ever met.
Just wondering - what was the point of this mail? That people subscribed
to maemo-developers & using bugzilla aren't users?
I'm just unclear how that's related to the bug jar,
Marius Gedminas escribió:
> On Thu, Jun 05, 2008 at 08:46:04AM +0200, Luca Olivetti wrote:
>> En/na Stephen Gadsby ha escrit:
>>
>>> 61 bugs were closed:
>> I noticed that some of the bugs are marked as "fixed in diablo", and
>> that's not really useful unless you release diablo rsn or provide
>>
Marius Gedminas wrote:
> Personally, I'm disappointed that when a bug is closed as "fixed in
> diablo", as a user I've no idea how to get the updated package on my
> N810.
Please excuse my disbelief ... you guys are the strangest "users" I've
ever met.
> I've got scratchbox handy,
In fact, "I'v
On Thu, Jun 05, 2008 at 08:46:04AM +0200, Luca Olivetti wrote:
> En/na Stephen Gadsby ha escrit:
>
> > 61 bugs were closed:
>
> I noticed that some of the bugs are marked as "fixed in diablo", and
> that's not really useful unless you release diablo rsn or provide
> updated packages for chinook
[EMAIL PROTECTED] escribió:
> FWIW, in Mozilla if someone says X is fixed, that just means there's a
> code fix, it doesn't mean it has passed through all verification steps.
And it's available in the next nightly, not hidden in a password
protected directory. And it's very probable that the nex
Frederic Crozat wrote:
> Remember that most people are not used to Nokia policy to embargo any
> date (even estimate) regarding software (or hardware) release.
For simplicity's sake, I don't know when Diablo will be released.
I also didn't know when Chinook was going to be released (in fact, I
bel
On Thu, Jun 5, 2008 at 9:51 AM, <[EMAIL PROTECTED]> wrote:
> Stephen Gadsby wrote:
>> 61 bugs were closed:
>
> Luca Olivetti wrote:
>> I noticed that some of the bugs are marked as "fixed in diablo", and
>> that's not really useful unless you release diablo rsn or provide
>> updated packages for c
Hi,
ext Luca Olivetti wrote:
> It's useful to know that a bug is fixed, what isn't useful is that the
> fix isn't actually available
In regular free software development a bug is generally solved when the
code is implemented and available somewhere. It's up to you to go to the
source and com
Stephen Gadsby wrote:
> A Quick Look at maemo Bugzilla
> 2008.05.29 through 2008.06.04
>
> As of 2008.06.04 maemo Bugzilla contains 3166 (+22 this week) items,
> including 1152 open issues (-40 this week):
> * 783 open bugs (-43 this week)
> * 9 critical/blocker (-3 this week)
> * 22 "
En/na [EMAIL PROTECTED] ha escrit:
> I suppose you think that black mail or threats is useful?
What makes you think that?
It's useful to know that a bug is fixed, what isn't useful is that the
fix isn't actually available
> As it happens, you can actually update your device to diablo prerel
En/na Eero Tamminen ha escrit:
> Hi,
>
> ext Luca Olivetti wrote:
>> En/na Stephen Gadsby ha escrit:
>>
>>> 61 bugs were closed:
>>
>> I noticed that some of the bugs are marked as "fixed in diablo", and
>> that's not really useful unless you release diablo rsn or provide
>> updated packages for
Eero wrote:
> I would like the close bug jar section to separate things that were
> marked as wontfix from things that were fixed (or worksforme).
seconded
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/list
Stephen Gadsby wrote:
> 61 bugs were closed:
Luca Olivetti wrote:
> I noticed that some of the bugs are marked as "fixed in diablo", and
> that's not really useful unless you release diablo rsn or provide
> updated packages for chinook.
I suppose you think that black mail or threats is useful?
Hi,
ext Luca Olivetti wrote:
> En/na Stephen Gadsby ha escrit:
>
>> 61 bugs were closed:
>
> I noticed that some of the bugs are marked as "fixed in diablo", and
> that's not really useful unless you release diablo rsn or provide
> updated packages for chinook.
I'm not sure everybody prefers
En/na Stephen Gadsby ha escrit:
> 61 bugs were closed:
I noticed that some of the bugs are marked as "fixed in diablo", and
that's not really useful unless you release diablo rsn or provide
updated packages for chinook.
Bye
--
Luca
___
maemo-develop
A Quick Look at maemo Bugzilla
2008.05.29 through 2008.06.04
As of 2008.06.04 maemo Bugzilla contains 3166 (+22 this week) items,
including 1152 open issues (-40 this week):
* 783 open bugs (-43 this week)
* 9 critical/blocker (-3 this week)
* 22 "moreinfo" (+4 this week)
*
28 matches
Mail list logo