ez-crew - more feedback / plz focus your work on stability / wishlist

Author Message

Georg Franz

Thursday 27 November 2003 7:29:50 am

Hi ez crew,

I've made a quick view to 3.3.0 beta - and I am unhappy.

Many ez users have made suggestions / have done a lot of bug reporting and it seems that only very few bugs are solved. (I spend a lot of time reporting bugs. Moreover if I find a solution I report the solution too. But I will stop doing this if my reports are ignored because in that case it's a waste of time.)

New features are nice to have (and - of course - I also want new features :) - but IMHO bug fixing is more important than new features.

I am currently working with ez 3.2.3 and IMHO this is the first version which is usable (of the 3.x series) - despite all bugs.

But I am sure that I can't use all the features of this version because I don't know them. The documention is [*censored*] [*censored*] [*censored*] [*censored*].

So, you have done 3.3, add some new features - and don't document them. Fine.

So my wishlist to ez (it's christmas soon ;-):

-) Focus your work on bug fixing
-) Answer to forum posts / bug reportings more frequent
-) Append your documentation
-) Wait for new releases until the doc. is updated.

Thanx!

Bye,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Karsten Jennissen

Thursday 27 November 2003 8:19:29 am

Could you be more specific about what bugs didn't get fixed?

Documentation: take your time and browse through it. There are a lot of gems in there. If you are unhappy, please consider writing things yourself. Documentation is Wiki style and contributed mainly by users.

Aleksander Farstad

Thursday 27 November 2003 8:19:40 am

Dear Emil,

Thank you for your feedback. You do certainly have many imporant points, that I would like to comment on how we are to solve these.

1) bug fixing: The time from now untill final release will only be spent on bugfixing, and yes we have not had time to fix many bugs in this beta, but we will close out all relevant bugs in the bug list before final. So please give us more feedback helping us better improve this release.

For the future: From the next development cycle (after 3.3 final) we will dedicate 1 person at all time for bugfixing and community communication (forums etc). This will make sure that we close all bugs when they come and not at the end of eah development cycle as now. We will then release a new release, i.e 3.3.2, once there have been enough fixed that it is reasonable for a new release. this will be done through the whole development cycle. We will also update the former version, i.e. 3.2.x untill the 3.4 release is done, and then 3.3.x until 3.5 is out etc.

2) Forum/bug lists: one dedicated person as stated above.

3) Documentation is focus and has been for a couple of months already. We have one person dedicated at documentation at all times, plus we will get into the development routines that all functions beeing made will be documented when made. But eZ publish is a very large project and it is lots of work to update the current docs, so please be patient.

So please be patient, we do hear you and all your requests, and thus are dedicating resources directly at this making sure we mature and stabilize the software, but still make sure it evolves.

Aleksander

Georg Franz

Thursday 27 November 2003 4:37:31 pm

Hi Aleksander,

thanx for your very quick answer. That sounds great!

Kind regards,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 15:14:25
Script start
Timing: Jan 18 2025 15:14:25
Module start 'layout'
Timing: Jan 18 2025 15:14:25
Module start 'content'
Timing: Jan 18 2025 15:14:25
Module end 'content'
Timing: Jan 18 2025 15:14:25
Script end

Main resources:

Total runtime0.0176 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0056 588.1719152.6563
Module start 'layout' 0.00560.0034 740.828139.5234
Module start 'content' 0.00900.0061 780.351693.3984
Module end 'content' 0.01500.0025 873.750034.3047
Script end 0.0175  908.0547 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002815.7356140.0002
Check MTime0.00116.4151140.0001
Mysql Total
Database connection0.00127.048110.0012
Mysqli_queries0.002614.771230.0009
Looping result0.00000.080110.0000
Template Total0.001910.810.0019
Template load0.00105.913910.0010
Template processing0.00084.831410.0008
Override
Cache load0.00084.317910.0008
General
dbfile0.00031.426280.0000
String conversion0.00000.044840.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs