Quim Gil wrote:
>
> About fixed bugs reported in the public bugzilla, we know we owe to the
> users and developers reporting those bugs a better response. The
> progress done in the last 6 months is remarkable but we are still not
> there. We tried but we couldn't have an updated report in the las
On Mon, 2007-08-06 at 17:21 +0300, Marius Vollmer wrote:
> "ext Guillem Jover" <[EMAIL PROTECTED]> writes:
>
> > What you seem to be asking for, is some kind of Release Notes, with
> > the most important package versions, or really big features.
>
> What is missing from my packages (and probably
On 8/6/07, Quim Gil <[EMAIL PROTECTED]> wrote:
>
> Just to clarify some roles here:
<-- snip -->
Take the best from each of us, that's my advice. We are just as good
> people and as well intentioned as you. And we work at Nokia, yes.
I probably haven't been lurking on this list long enough to
"ext Guillem Jover" <[EMAIL PROTECTED]> writes:
> What you seem to be asking for, is some kind of Release Notes, with
> the most important package versions, or really big features.
What is missing from my packages (and probably others) is a properly
maintained NEWS file, and maybe a channel to ma
Hi,
Lauri Leukkunen wrote:
> On 06/08/07 16:10 +0300, ext Eero Tamminen wrote:
>> * _No_ other distro is providing bugfix list for releases, so I don't
>> see why it's so huge deal Maemo not providing one either.
>
> I guess it's a deal for those who want to maintain another distro based
> on
On 06/08/07 16:10 +0300, ext Eero Tamminen wrote:
> * _No_ other distro is providing bugfix list for releases, so I don't
> see why it's so huge deal Maemo not providing one either.
I guess it's a deal for those who want to maintain another distro based
on the maemo components but not the packa
Hi,
(as always, my own opinions, not Nokia's)
ext Andy Mulhearn wrote:
> Hmmm, I think someone's missing the point here. You "Nokia" tell me as
> an end user nothing about what's in each release. From start to finish,
> there's no information in a release that tells me what it includes. At
> the
Just to clarify some roles here:
- Some people like Daniel are developing specific stuff for maemo. You
can ask, suggest, criticize and they will probably answer to the best of
their knowledge and time about the areas they work in. They might
eventually scale up and discuss some maemo or Nokia wid
On Mon, Aug 06, 2007 at 12:21:24PM +0200, ext Koen Kooi wrote:
> Makes me sad when nokia (employees) don't tell us enough and then try
> guilting us into
> shutting up with statements like the above.
Hi,
It's pretty easy to just see Nokia as a nameless, faceless corporation
responsible for all th
Hi, back from holidays.
mmm where to start
On Fri, 2007-08-03 at 20:23 +0100, ext Andy Mulhearn wrote:
> You "Nokia" tell me
> as an end user nothing about what's in each release. From start to
> finish, there's no information in a release that tells me what it
> includes.
Let's see what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] schreef:
>> To be honest, your response is more along the same line of the
>> previous responses, i.e. "it's more complex than you understand"
>> which again just tells me Nokia either can't or won't provide
>> this information.
>>> How about all of them?
>>
>> Please check what's available; kernel and X git repositories you
>> should find with Google, Application framework stuff you will find
>> from Maemo (until it's moved to Gnome), new Browser is in
>Garage. For
>> all the open
>> source(d) packages you find the d
On Fri, Aug 03, 2007 at 06:32:07PM +0300, Eero Tamminen wrote:
> Please check what's available; kernel and X git repositories you should
> find with Google
Actually, you can't find the X git repository. This is partially
because I can't publish the one I use for actual development, as it
contains
On Fri, Aug 03, 2007 at 06:19:40PM +0100, ext Neil MacLeod wrote:
> Let's face it, the existence of two bug tracking systems (one internal and
> one public) isn't helping matters
This is a basic requirement of corporate security, for reasons I assumed
were obvious, but given that they apparently
On 3 Aug 2007, at 20:30, Koen Kooi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Andy Mulhearn schreef:
>
>>> I understood the problem being discussed here is how to map that to
>>> public releases and for end-users? As Quim stated, this is being
>>> (slowly) improved.
>>
>> If sl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Mulhearn schreef:
>> I understood the problem being discussed here is how to map that to
>> public releases and for end-users? As Quim stated, this is being
>> (slowly) improved.
>
> If slow improvement means not seeing any change over a period
On 3 Aug 2007, at 16:32, Eero Tamminen wrote:
> Hi,
>
> ext Andy Mulhearn wrote:
>> On Thursday, August 02, 2007, at 12:11PM, "Daniel Stone"
>> <[EMAIL PROTECTED]> wrote:
>>> On Thu, Aug 02, 2007 at 02:05:31AM -0700, ext Andy Mulhearn wrote:
On Thursday, August 02, 2007, at 09:56AM, "Eero
Eero Tamminen wrote:
> It's not so much "withholding" the information as getting
> somebody spending large effort on collecting, filtering/reducing
> and translating this information to publicly relevant/usable form.
>
"Someone" only has to spend a large effort on collecting, filtering etc. *IF*
On 8/3/07, Guillem Jover <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-08-03 at 16:39:07 +0100, ext Andrew Flegg wrote:
> > On 8/3/07, Eero Tamminen <[EMAIL PROTECTED]> wrote:
> > > Please check what's available; kernel and X git repositories you
> > > should find with Google, [...]
>
> > OK, so the on
Hi,
On Fri, 2007-08-03 at 16:39:07 +0100, ext Andrew Flegg wrote:
> On 8/3/07, Eero Tamminen <[EMAIL PROTECTED]> wrote:
> > Please check what's available; kernel and X git repositories you should
> > find with Google, Application framework stuff you will find from Maemo
> > (until it's moved to Gn
On 8/3/07, Eero Tamminen <[EMAIL PROTECTED]> wrote:
>
> Please check what's available; kernel and X git repositories you should
> find with Google, Application framework stuff you will find from Maemo
> (until it's moved to Gnome), new Browser is in Garage. For all the open
> source(d) packages yo
Hi,
ext Andy Mulhearn wrote:
> On Thursday, August 02, 2007, at 12:11PM, "Daniel Stone" <[EMAIL PROTECTED]>
> wrote:
>> On Thu, Aug 02, 2007 at 02:05:31AM -0700, ext Andy Mulhearn wrote:
>>> On Thursday, August 02, 2007, at 09:56AM, "Eero Tamminen" <[EMAIL
>>> PROTECTED]> wrote:
We certainl
Eero Tamminen wrote:
> It's about the amount of work needed from reducing the "raw"
> list of all internal bugfixes which:
> - is way too large for anybody to digest as such
> - 99% of it would be fixes to bugs that are not present in
> _any_ of the public releases
> - has items which don't tell
Hi,
First I should mention that I was discussing only bugfixes,
I agree that features should be listed, but I've understood
from Quim's mail that this should be already improving.
(Like all my other mails on this list, these are personal opinions.)
ext Neil MacLeod wrote:
>> We certainly know wh
Eero Tamminen wrote:
> Hi,
>
> We certainly know what we've fixed, but the issue is that there's
> no reasonable way to know what part of that is relevant to you.
>
At the very least publish those bugs that are aliased to bugs in the Public
bugzilla. You have the public bugs aliased to internal
On Thursday, August 02, 2007, at 12:11PM, "Daniel Stone" <[EMAIL PROTECTED]>
wrote:
>On Thu, Aug 02, 2007 at 02:05:31AM -0700, ext Andy Mulhearn wrote:
>> On Thursday, August 02, 2007, at 09:56AM, "Eero Tamminen" <[EMAIL
>> PROTECTED]> wrote:
>> >We certainly know what we've fixed, but the issu
On Thu, Aug 02, 2007 at 02:05:31AM -0700, ext Andy Mulhearn wrote:
> On Thursday, August 02, 2007, at 09:56AM, "Eero Tamminen" <[EMAIL PROTECTED]>
> wrote:
> >We certainly know what we've fixed, but the issue is that there's
> >no reasonable way to know what part of that is relevant to you.
>
> W
On Thursday, August 02, 2007, at 09:56AM, "Eero Tamminen" <[EMAIL PROTECTED]>
wrote:
>Hi,
>
>ext Neil MacLeod wrote:
>> Quim Gil wrote:
>>> On Sat, 2007-07-07 at 18:41 +0100, ext Neil MacLeod wrote:
>>> By Diablo, perhaps. We hope so.
>>
>> I should hope it should be possible to release somethi
Hi,
ext Neil MacLeod wrote:
> Quim Gil wrote:
>> On Sat, 2007-07-07 at 18:41 +0100, ext Neil MacLeod wrote:
>> By Diablo, perhaps. We hope so.
>
> I should hope it should be possible to release something as basic as
> a changelog by v5 of a project. I know that sounds harsh, but seriously...
> if
On Mon, 2007-07-09 at 08:36 +0300, Quim Gil wrote:
> Something that would help are links to your preferred release notes. Yes
> we know that in principle the more details the better, but providing
> examples of non-exhaustive yet satisfactory release notes you like and
> find useful would help us f
On Mon, 2007-07-09 at 06:45 +0100, ext Neil MacLeod wrote:
> I should hope it should be possible to release something as basic as a
> changelog by v5 of a project.
It's not about versions but about integrating/coordinating our internal
development process with http://bugs.maemo.org . This is what
Quim Gil wrote:
> On Sat, 2007-07-07 at 18:41 +0100, ext Neil MacLeod wrote:
> By Diablo, perhaps. We hope so.
I should hope it should be possible to release something as basic as a
changelog by v5 of a project. I know that sounds harsh, but seriously... if you
don't what you've fixed in any giv
On Sat, 2007-07-07 at 18:41 +0100, ext Neil MacLeod wrote:
> Are there any plans to publish a detailed changelog for 4.2007.26-8?
Nope, sorry. We have tried but our internal process is not ready for
this, yet. We have improved providing more details than before about the
new features implemented.
[EMAIL PROTECTED] wrote:
>> Did you (or anyone else) manage to make any progress on a
>> changelog for 3.2007.10-7?
>
> I have started the internal discussion with the aim of having a
> changelog linking to maemo's bugzilla being published together with the
> next IT OS release notes. And improve
>Did you (or anyone else) manage to make any progress on a
>changelog for 3.2007.10-7?
I have started the internal discussion with the aim of having a
changelog linking to maemo's bugzilla being published together with the
next IT OS release notes. And improve from that point in next releases.
[EMAIL PROTECTED] wrote:
On Behalf Of ext Neil MacLeod
Would it be possible to provide a detailed change log for
3.2007.10-7, ideally cross-referenced with the public Bugzilla
so that we (the users) known which of those bugs we have
raised have been addressed?
The published change log is ex
On Wed, 2007-03-28 at 18:15 +0200, ext Murray Cumming wrote:
> On Wed, 2007-03-28 at 14:16 +0300, [EMAIL PROTECTED] wrote:
> > Do not give up on it just yet, it is changing for better. We have a real
> > person behind [EMAIL PROTECTED] If not counting enhancement requests and
> > reports on closed
On Wed, 2007-03-28 at 14:16 +0300, [EMAIL PROTECTED] wrote:
> >Daniel Stone wrote:
> >
> >> You got it. The majority of the bug work happens before product
> >> release: going by what's in the changelogs, the external
> >database has
> >> roughly 2% of the bugs as the internal one.
> >
> >That m
[EMAIL PROTECTED] wrote:
Hi,
Do not give up on it just yet, it is changing for better. We have a real
person behind [EMAIL PROTECTED] If not counting enhancement requests and
reports on closed applications then almost all new bug reports get
handled.
Jakke is quite active! :)
What is still
>Daniel Stone wrote:
>
>> You got it. The majority of the bug work happens before product
>> release: going by what's in the changelogs, the external
>database has
>> roughly 2% of the bugs as the internal one.
>
>That might well be because I (and others) have given up on
>using the external bu
On Wed, 2007-03-28 at 11:41 +0200, ext Sebastian Spaeth wrote:
> Daniel Stone wrote:
>
> > You got it. The majority of the bug work happens before product
> > release: going by what's in the changelogs, the external database has
> > roughly 2% of the bugs as the internal one.
>
> That might well
Daniel Stone wrote:
> You got it. The majority of the bug work happens before product
> release: going by what's in the changelogs, the external database has
> roughly 2% of the bugs as the internal one.
That might well be because I (and others) have given up on using the
external bug database a
On Tue, Mar 27, 2007 at 10:22:25AM -0500, ext Paul Klapperich wrote:
> I think the ideal situation would be if the public bugzilla was used by
> Nokia when fixing bugs submitted publicly and the internal bugzilla used
> when fixing bugs Nokia feels need to be hidden from public view for whatever
>
On 3/27/07, Neil MacLeod <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> Hi all,
>
> This sounds like something technically easy to do (for Nokia):
> 1) get all the internal bugs we have fixed
> 2) extract the referrences to public bugzilla
> 3) make sure all the public bugzilla bugs are m
[EMAIL PROTECTED] wrote:
Hi all,
This sounds like something technically easy to do (for Nokia):
1) get all the internal bugs we have fixed
2) extract the referrences to public bugzilla
3) make sure all the public bugzilla bugs are marked as FIXED the same
day we release the update
And as a bonu
Hi all,
This sounds like something technically easy to do (for Nokia):
1) get all the internal bugs we have fixed
2) extract the referrences to public bugzilla
3) make sure all the public bugzilla bugs are marked as FIXED the same
day we release the update
And as a bonus lets list the public bugs
>Would it be possible to provide a detailed change log for
>3.2007.10-7, ideally cross-referenced with the public Bugzilla
>so that we (the users) known which of those bugs we have
>raised have been addressed?
Good question. I will try to answer officially as soon as possible. I
mean, the answe
Would it be possible to provide a detailed change log for 3.2007.10-7, ideally
cross-referenced with the public Bugzilla so that we (the users) known which of
those bugs we have raised have been addressed?
The published change log is extremely inadequate, unfortunately.
Many thanks...
___
48 matches
Mail list logo
