Hi!
Not sure there is a lot to status report, but I try:
- the number of incoming bugs is growing, for some
components almost dramatically. So much time is
spent in screening at the moment. For a glimpse,
check http://tinyurl.com/2cxbto
(you're very welcome to help screening duplicates)
Stephan Kulow wrote:
> Hi!
>
> Not sure there is a lot to status report, but I try:
>
> - the number of incoming bugs is growing, for some
> components almost dramatically. So much time is
> spent in screening at the moment. For a glimpse,
> check http://tinyurl.com/2cxbto
> (you're very
Am Mittwoch 31 Oktober 2007 schrieb Wolfgang Rosenauer:
> Stephan Kulow wrote:
> > Hi!
> >
> > Not sure there is a lot to status report, but I try:
> >
> > - the number of incoming bugs is growing, for some
> > components almost dramatically. So much time is
> > spent in screening at the moment
> > I think bug reporters and testers did their job during the development
> > stage, the bug slashing weekend and the community contribution to 10.3
> > were probably the biggest since the birth of the project.
> >
> > As a consequence, I think some more effort to fix at least the most
> > annoyi
Stephan Kulow wrote:
> Hi!
>
> Not sure there is a lot to status report, but I try:
>
> - the number of incoming bugs is growing, for some
> components almost dramatically. So much time is
> spent in screening at the moment. For a glimpse,
> check http://tinyurl.com/2cxbto
> (you're very
Am Mittwoch 31 Oktober 2007 schrieb Ken Schneider:
> Stephan Kulow wrote:
> > Hi!
> >
> > Not sure there is a lot to status report, but I try:
> >
> > - the number of incoming bugs is growing, for some
> > components almost dramatically. So much time is
> > spent in screening at the moment. For
Hi,
> Are there any plans to publish the fix to yast2-ntp-client as an
> update to 10.3 ?
The issue should be fixed by now, however it's not up to me to decide whether
it is worth online update :) The bug does not affect functionality at all,
just these repository scanning popups might be annoy
2007/10/31, Katarina Machalkova <[EMAIL PROTECTED]>:
> Hi,
>
> > Are there any plans to publish the fix to yast2-ntp-client as an
> > update to 10.3 ?
>
> The issue should be fixed by now, however it's not up to me to decide whether
> it is worth online update :) The bug does not affect functionali
Raúl Moratalla wrote:
> Thank you for packaging smoke and qyoto. I installed them, but the package of
> qyoto is missing some files: the assembly (qt-dotnet.dll) and
> qt-dotnet.dll.mdb (I don't know if this file is needed).
That's exact problem I was expecting. I have never packaged a mono
pack
Marcus Rueckert wrote:
> why not in the KDE:Qt4 project?
There is no KDE:Qt4 project, only KDE:Qt. If this is what you meant,
could you please add me as a maintainer? I will move packages ASAP. And
if somebody creates Jambi bindings, they could be put there as well.
--
Best Regards / S pozdravom
Stephan Kulow wrote:
> Am Mittwoch 31 Oktober 2007 schrieb Ken Schneider:
>> Stephan Kulow wrote:
>>> Hi!
>>>
>>> Not sure there is a lot to status report, but I try:
>>>
>>> - the number of incoming bugs is growing, for some
>>> components almost dramatically. So much time is
>>> spent in scre
Am Mittwoch 31 Oktober 2007 schrieb Ken Schneider:
> > This would require remastering 10.3 and we want to avoid that.
>
> How is that? Deltas are used all the time to update the alpha/beta
> releases, how is this different? Just curious.
When we master a new alpha, we create a delta to the last one
Stephan Kulow wrote:
> Am Mittwoch 31 Oktober 2007 schrieb Ken Schneider:
>
>>> This would require remastering 10.3 and we want to avoid that.
>>>
>> How is that? Deltas are used all the time to update the alpha/beta
>> releases, how is this different? Just curious.
>>
> When we mast
Am Mittwoch 31 Oktober 2007 schrieb Roberto Mannai:
> Hi Stephan,
> why does the report start from november 2006? Which products are you
> considering? I cannot understand what are you measuring; open bug of
> course grow in the time; it would be more meaningful to show the ratio
> between open / c
Hi Stephan,
why does the report start from november 2006? Which products are you
considering? I cannot understand what are you measuring; open bug of
course grow in the time; it would be more meaningful to show the ratio
between open / closed in each component, and resolution type.
Best regards
Ro
As a user and if searching which distro to choose, I would be
interested to see how many bugs are closed for that distro, so seeing
how much support is given.
Of course, a report stems from data and purpose of search, so if you
want to see the total number of bug open from 2006 it is ok for me :)
I think so :).
So are you measuring the delta Y (size of bugs open) between X and (X
- 1) of time?
On 10/31/07, Stephan Kulow <[EMAIL PROTECTED]> wrote:
> Am Mittwoch 31 Oktober 2007 schrieb Roberto Mannai:
> > As a user and if searching which distro to choose, I would be
> > interested to see h
Am Mittwoch 31 Oktober 2007 schrieb Roberto Mannai:
> I think so :).
>
> So are you measuring the delta Y (size of bugs open) between X and (X
> - 1) of time?
>
I just let bugzilla plot the number of open bugs over the days.
Greetings, Stephan
-
Am Mittwoch 31 Oktober 2007 schrieb Roberto Mannai:
> As a user and if searching which distro to choose, I would be
> interested to see how many bugs are closed for that distro, so seeing
> how much support is given.
>
Those users will hardly read opensuse-factory I'd assume.
Greetings, Stephan
-
On Wed, 31 Oct 2007, Richard Creighton wrote:
> Stephan Kulow wrote:
> > Am Mittwoch 31 Oktober 2007 schrieb Ken Schneider:
> >>> This would require remastering 10.3 and we want to avoid that.
> >> How is that? Deltas are used all the time to update the alpha/beta
> >> releases, how is this differe
Am Mittwoch 31 Oktober 2007 schrieb Boyd Lynn Gerber:
> I do not know anyone that is able to use the repair system. I am talking
> about aprox... 200 users. This to me is a major pita. I really think
> that we should get a delta. I really need to create new iso's. I am
> getting pestered becau
21 matches
Mail list logo
