Greatly improved bug feedback

Next topic

Author	Message
Paul Forsyth	Thursday 03 July 2003 5:30:31 am Are there plans to improve the way bugs are handled in the future? I've just read the 3.2 release plan and notice that, like with the 3.1 release plan, all known bugs will be fixed for that release. Since that hasn't happened with 3.1 (although a lot were fixed...) it would be very nice to get feedback on what the state of affairs are with current outstanding bugs. Tools such as bugzilla allow users to see developers comments and add to the conversation. I think the current bug reports needs more transparency since we cannot see: - if anyone is working on a bug - what they think of it - whether its likely to get fixed for the next release - etc, etc. This is in addition to a ui revamp. What do ez use internally for handling bugs? I can't believe ez would use the ez.no bug interface. paul
Bård Farstad	Thursday 03 July 2003 6:29:25 am We will improve the bugdatabase on ez.no. We just need some of the 3.2 features for the bugdatabase. We will most likely get this done in the testing period of 3.2, where we will upgrade ez.no and test out the filtering and sorting functionality. UI will also get an overhaul then. SVN commit log will also be added again, we had to remove it because of problems with svn. This will come. Internally we used to use eZ publish 2.2 and other systems like excel spreadsheets. Mostly we use an internal mailinglist, we are trying to get more and more of this information out on ez.no. --bård Documentation: http://ez.no/doc
Tony Wood	Tuesday 08 July 2003 3:53:41 am One thing that would be nice is, my bugs list, so you can track the progress on the bugs that you posted. Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Author

Message

Thursday 03 July 2003 5:30:31 am

Are there plans to improve the way bugs are handled in the future?

I've just read the 3.2 release plan and notice that, like with the 3.1 release plan, all known bugs will be fixed for that release. Since that hasn't happened with 3.1 (although a lot were fixed...) it would be very nice to get feedback on what the state of affairs are with current outstanding bugs.

Tools such as bugzilla allow users to see developers comments and add to the conversation. I think the current bug reports needs more transparency since we cannot see:

- if anyone is working on a bug
- what they think of it
- whether its likely to get fixed for the next release
- etc, etc.

This is in addition to a ui revamp.

What do ez use internally for handling bugs? I can't believe ez would use the ez.no bug interface.

paul

Bård Farstad

Thursday 03 July 2003 6:29:25 am

We will improve the bugdatabase on ez.no. We just need some of the 3.2 features for the bugdatabase. We will most likely get this done in the testing period of 3.2, where we will upgrade ez.no and test out the filtering and sorting functionality. UI will also get an overhaul then.

SVN commit log will also be added again, we had to remove it because of problems with svn. This will come.

Internally we used to use eZ publish 2.2 and other systems like excel spreadsheets. Mostly we use an internal mailinglist, we are trying to get more and more of this information out on ez.no.

--bård

Documentation: http://ez.no/doc

Tony Wood

Tuesday 08 July 2003 3:53:41 am

One thing that would be nice is, my bugs list, so you can track the progress on the bugs that you posted.

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

eZ debug

Timing:	Jan 18 2025 10:25:18
Script start
Timing:	Jan 18 2025 10:25:18
Module start 'layout'
Timing:	Jan 18 2025 10:25:18
Module start 'content'
Timing:	Jan 18 2025 10:25:19
Module end 'content'
Timing:	Jan 18 2025 10:25:19
Script end

Main resources:

Total runtime	0.4933 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0087	589.0313	152.6250
Module start 'layout'	0.0087	0.0038	741.6563	39.4453
Module start 'content'	0.0124	0.4793	781.1016	577.7734
Module end 'content'	0.4917	0.0016	1,358.8750	12.1641
Script end	0.4933		1,371.0391

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.7266	16	0.0002
Check MTime	0.0015	0.3041	16	0.0001
Mysql Total
Database connection	0.0012	0.2438	1	0.0012
Mysqli_queries	0.4299	87.1334	59	0.0073
Looping result	0.0006	0.1285	57	0.0000
Template Total	0.4468	90.6	2	0.2234
Template load	0.0022	0.4397	2	0.0011
Template processing	0.4446	90.1232	2	0.2223
Template load and register function	0.0002	0.0438	1	0.0002
states
state_id_array	0.0012	0.2402	1	0.0012
state_identifier_array	0.0017	0.3483	2	0.0009
Override
Cache load	0.0018	0.3646	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.1263	3	0.0002
Fetch class attribute name	0.0015	0.2979	5	0.0003
XML
Image XML parsing	0.0012	0.2361	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0021	5	0.0000
General
dbfile	0.0008	0.1712	23	0.0000
String conversion	0.0000	0.0016	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 12 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs