Better release notes

Next topic

Author	Message
Paul Forsyth	Thursday 28 August 2003 1:03:51 am Could the release notes for version (betas, rcs, final) be rewritten to describe better what has changed between versions? I forgot to mention this at the conference but it would be great if we didn't have a massive list of changes that has come direct from svn commits. I would like to see an overview for individual sections that have changed discussing what is new and what bugs have been fixed (urls,ids preferrably). For example, the current kernel change list needs to be split up into affect parts of the kernel. Also it would be nice if known issues are published for that version, issues you may have found during testing but have workarounds that you recommend. The changelog should still be there but referenced in some way from each section. This information will really help people looking to migrate between versions. As ez 3 becomes more stable and ez 4 starts to be thought about users need better information about changes between versions. Paul
Jan Borsodi	Thursday 28 August 2003 4:03:02 am You mean like a compact summary of important changes? Should this be a part of the release (like Changelogs) or as a document on ez.no? -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Paul Forsyth	Thursday 28 August 2003 4:34:58 am Most software releases provide the same document with the release as they have on their website, whether it is as a .txt or a .html file, so one version should be fine. Yes a summary of important changes to each area would be nice. For example, the 3.2 beta release has many changes to the kernel which may affect developers working with the 3.1 sdk, translations, so speaking about the big changes there, api's and so on would be lovely. At the very least it should be able to tell developers that they should look at what changes have occured. A big all-in-one list obscures the changes. Of course, you need to balance what users will be interested in low level changes :) I would like to see good high level summaries with discussion of changes within modules, libs and kernels areas and the apis used to communicate between each. The svn list currently has some seperation between areas. If this was augmented with further information along the above lines that would be great. Paul
Paul Forsyth	Thursday 04 September 2003 1:27:32 am Thanks for the 3.2 beta 2 release documentation. I really like the new format! Though I have a couple of gripes, wishes... :) Could the level of detail be improved to state which areas are affected by updates. I notice a few obscure mentions of sdk changes. Could these be specifially assigned to an area, and maybe expanded upon? Most of the changes seem to be for users but i know sdk changes have been occurring. Do you have a list of known issues with a release that you have found through your testing phase? Could the larger issues be posted as part of a release? As Paul B mentions in his comment to the beta2 release the svn log was handy... Im not sure if it is good to include the full changelog as before in the same document. Maybe there should be a seperate document listing the changelogs for all releases... I've seen this used on other projects. Paul

eZ debug

Timing:	Jan 18 2025 11:12:20
Script start
Timing:	Jan 18 2025 11:12:20
Module start 'layout'
Timing:	Jan 18 2025 11:12:20
Module start 'content'
Timing:	Jan 18 2025 11:12:21
Module end 'content'
Timing:	Jan 18 2025 11:12:21
Script end

Main resources:

Total runtime	1.3576 sec
Peak memory usage	4,096.0000 KB
Database Queries	60

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0069	589.0391	152.6250
Module start 'layout'	0.0069	0.0051	741.6641	39.4297
Module start 'content'	0.0120	1.3443	781.0938	545.3203
Module end 'content'	1.3562	0.0014	1,326.4141	12.1875
Script end	1.3576		1,338.6016

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.2495	16	0.0002
Check MTime	0.0014	0.1027	16	0.0001
Mysql Total
Database connection	0.0011	0.0788	1	0.0011
Mysqli_queries	1.3020	95.9010	60	0.0217
Looping result	0.0009	0.0669	58	0.0000
Template Total	1.3170	97.0	2	0.6585
Template load	0.0022	0.1630	2	0.0011
Template processing	1.3148	96.8432	2	0.6574
Template load and register function	0.0002	0.0178	1	0.0002
states
state_id_array	0.0008	0.0583	1	0.0008
state_identifier_array	0.0028	0.2056	2	0.0014
Override
Cache load	0.0018	0.1318	26	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0462	2	0.0003
Fetch class attribute name	0.0018	0.1330	5	0.0004
XML
Image XML parsing	0.0007	0.0511	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0010	5	0.0000
General
dbfile	0.0008	0.0598	17	0.0000
String conversion	0.0000	0.0007	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
4	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/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: 11 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs