Re: Bugzilla upgrade.

2012-03-15 Thread David Jarvie
On Wed, March 14, 2012 9:41 pm, Burkhard Lück wrote:
 And to have the Additional Comments field above the BR and all comments
 is like tofu (http://en.wikipedia.org/wiki/Top-posting#Top-posting)

There is now a preference setting which lets you choose whether to display
the Additional Comments field at the top or the bottom.

On Wed, March 14, 2012 7:32 pm, Daniel Nicoletti wrote:
 I don't think so, I think it has some huge icons but I thought
 it was my browsers problem, the huge header and footer
 it's real hard to see the content on my small screen,
 the new version fews snappier but the theme needs polishing
 imo. I also renders the footer strange using Chrome,
 but I hope someone is still working on this... :D

Yes, the header fields waste a _lot_ of space. The old theme was far
better in that respect.

-- 
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm



Re: Bugzilla upgrade.

2012-03-15 Thread Boudewijn Rempt
On Thursday 15 March 2012 Mar, David Jarvie wrote:
 On Wed, March 14, 2012 9:41 pm, Burkhard Lück wrote:
  And to have the Additional Comments field above the BR and all comments
  is like tofu (http://en.wikipedia.org/wiki/Top-posting#Top-posting)
 
 There is now a preference setting which lets you choose whether to display
 the Additional Comments field at the top or the bottom.
 
 On Wed, March 14, 2012 7:32 pm, Daniel Nicoletti wrote:
  I don't think so, I think it has some huge icons but I thought
  it was my browsers problem, the huge header and footer
  it's real hard to see the content on my small screen,
  the new version fews snappier but the theme needs polishing
  imo. I also renders the footer strange using Chrome,
  but I hope someone is still working on this... :D
 
 Yes, the header fields waste a _lot_ of space. The old theme was far
 better in that respect.

And the footer field tends to obscure the line I was searching for, at least in 
firefox. 

-- 
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl


Re: Bugzilla upgrade.

2012-03-14 Thread Dawit A
Am I the only one that finds the new KDE bugzilla front end utterly
confusing ? All the conveient shortcuts in the front page that showed
things like weekly summary broken down by product are no longer
available. Will those things available in the old front page be
restored in the future or are they gone for good ?


Re: Bugzilla upgrade.

2012-03-14 Thread Burkhard Lück
Am Mittwoch, 14. März 2012, 20:13:18 schrieb Dawit A:
 Am I the only one that finds the new KDE bugzilla front end utterly
 confusing ? 

No, me too.

 All the conveient shortcuts in the front page that showed
 things like weekly summary broken down by product are no longer
 available. 

I really miss them.

And to have the Additional Comments field above the BR and all comments is 
like tofu (http://en.wikipedia.org/wiki/Top-posting#Top-posting)

The new front end / layout is really disturbing  for my daily workflow looking 
for all bugs related to documentation, i18n, l10n and reports I can quickly 
check in master/branch/my distribution packages reported the last day.. 

-- 
Burkhard Lück


Re: Bugzilla upgrade.

2012-03-14 Thread Daniel Nicoletti
I don't think so, I think it has some huge icons but I thought
it was my browsers problem, the huge header and footer
it's real hard to see the content on my small screen,
the new version fews snappier but the theme needs polishing
imo. I also renders the footer strange using Chrome,
but I hope someone is still working on this... :D

2012/3/14 Dawit A ada...@kde.org:
 Am I the only one that finds the new KDE bugzilla front end utterly
 confusing ? All the conveient shortcuts in the front page that showed
 things like weekly summary broken down by product are no longer
 available. Will those things available in the old front page be
 restored in the future or are they gone for good ?


Re: Bugzilla upgrade.

2012-02-24 Thread Andras Mantia
On Tuesday, February 21, 2012 11:37:23 PM Milian Wolff wrote:
 What version will the new bugzilla have? Are the REST/JSON/XMLRPC APIs
 going  to be enabled?

And then maybe someone can revive kbugbuster.

Andras



Re: Bugzilla upgrade.

2012-02-22 Thread Marc Deop
On Wednesday 22 February 2012 11:47:36 Ben Cooksley wrote:
 We will likely be upgrading to the latest version of the 4.x series.

Make sure it's the 4.0.4 as it solves some issues with the perl packages 
related to JSON (versioning problems)

 We have not deliberately disabled REST/JSON/XMLRPC in the past, and
 will not do so with this update.

Keep in mind the JSON-RPC is marked as experimental by the bugzilla team 
(experimental as in they think the API won't change in the future although it 
still might). The stable api is the XML-RPC


Bugzilla upgrade.

2012-02-21 Thread Tom Albers
Hi, 

Our bugzilla instance is an old version. We are preparing to upgrade it to a 
recent version. 

This will go in two stages. First we will perform a test upgrade. This will 
happen on Saturday Februari 25th. We will start at 8PM CET. We expect little 
inpact, though during the database conversion we expect the current bugzilla to 
be slower as usual. If this will becomes unworkable, we will close bugs.kde.org 
during this conversion. 

If all goes well, we want to do the final conversion on Friday March 2nd. We 
will start at 8PM CET. During the conversion bugs.kde.org will be unavailable. 
We expect a downtime of a few hours. We will know more after the test.

All work will be coordinated via the #kde-sysadmin. If you want to test the new 
bugzilla before it goes live (/me waves at the dr.konqi developers) talk to us. 
Also when you have any other concerns or questions about the upgrade.

Best,

Tom Albers
KDE Sysadmin
ps. Any replies which include the word 'Redmine' will be ignored.


Re: Bugzilla upgrade.

2012-02-21 Thread Milian Wolff
On Tuesday 21 February 2012 21:00:33 Tom Albers wrote:
 Hi,
 
 Our bugzilla instance is an old version. We are preparing to upgrade it to a
 recent version.
 
 This will go in two stages. First we will perform a test upgrade. This will
 happen on Saturday Februari 25th. We will start at 8PM CET. We expect
 little inpact, though during the database conversion we expect the current
 bugzilla to be slower as usual. If this will becomes unworkable, we will
 close bugs.kde.org during this conversion.
 
 If all goes well, we want to do the final conversion on Friday March 2nd. We
 will start at 8PM CET. During the conversion bugs.kde.org will be
 unavailable. We expect a downtime of a few hours. We will know more after
 the test.
 
 All work will be coordinated via the #kde-sysadmin. If you want to test the
 new bugzilla before it goes live (/me waves at the dr.konqi developers)
 talk to us. Also when you have any other concerns or questions about the
 upgrade.

What version will the new bugzilla have? Are the REST/JSON/XMLRPC APIs going 
to be enabled?

Bye and many thanks for giving our bug-pit some love!
-- 
Milian Wolff
m...@milianw.de
http://milianw.de

signature.asc
Description: This is a digitally signed message part.


Re: Bugzilla upgrade.

2012-02-21 Thread Ben Cooksley
On Wed, Feb 22, 2012 at 11:37 AM, Milian Wolff m...@milianw.de wrote:
 On Tuesday 21 February 2012 21:00:33 Tom Albers wrote:
 Hi,

 Our bugzilla instance is an old version. We are preparing to upgrade it to a
 recent version.

 This will go in two stages. First we will perform a test upgrade. This will
 happen on Saturday Februari 25th. We will start at 8PM CET. We expect
 little inpact, though during the database conversion we expect the current
 bugzilla to be slower as usual. If this will becomes unworkable, we will
 close bugs.kde.org during this conversion.

 If all goes well, we want to do the final conversion on Friday March 2nd. We
 will start at 8PM CET. During the conversion bugs.kde.org will be
 unavailable. We expect a downtime of a few hours. We will know more after
 the test.

 All work will be coordinated via the #kde-sysadmin. If you want to test the
 new bugzilla before it goes live (/me waves at the dr.konqi developers)
 talk to us. Also when you have any other concerns or questions about the
 upgrade.

 What version will the new bugzilla have? Are the REST/JSON/XMLRPC APIs going
 to be enabled?

We will likely be upgrading to the latest version of the 4.x series.
We have not deliberately disabled REST/JSON/XMLRPC in the past, and
will not do so with this update.


 Bye and many thanks for giving our bug-pit some love!
 --
 Milian Wolff
 m...@milianw.de
 http://milianw.de

Regards,
Ben


Re: Bugzilla upgrade.

2012-02-21 Thread Milian Wolff
On Wednesday 22 February 2012 11:47:36 Ben Cooksley wrote:
 On Wed, Feb 22, 2012 at 11:37 AM, Milian Wolff m...@milianw.de wrote:
  On Tuesday 21 February 2012 21:00:33 Tom Albers wrote:
  Hi,
  
  Our bugzilla instance is an old version. We are preparing to upgrade it
  to a recent version.
  
  This will go in two stages. First we will perform a test upgrade. This
  will
  happen on Saturday Februari 25th. We will start at 8PM CET. We expect
  little inpact, though during the database conversion we expect the
  current
  bugzilla to be slower as usual. If this will becomes unworkable, we will
  close bugs.kde.org during this conversion.
  
  If all goes well, we want to do the final conversion on Friday March 2nd.
  We will start at 8PM CET. During the conversion bugs.kde.org will be
  unavailable. We expect a downtime of a few hours. We will know more after
  the test.
  
  All work will be coordinated via the #kde-sysadmin. If you want to test
  the
  new bugzilla before it goes live (/me waves at the dr.konqi developers)
  talk to us. Also when you have any other concerns or questions about the
  upgrade.
  
  What version will the new bugzilla have? Are the REST/JSON/XMLRPC APIs
  going to be enabled?
 
 We will likely be upgrading to the latest version of the 4.x series.
 We have not deliberately disabled REST/JSON/XMLRPC in the past, and
 will not do so with this update.

Cool, thanks!

bye
-- 
Milian Wolff
m...@milianw.de
http://milianw.de

signature.asc
Description: This is a digitally signed message part.