[Kolab-devel] Branch '2.3-stable' - pear/Kolab_Storage release-notes.txt

[Gunnar Wrobel]

Quoting Gunnar Wrobel <wrobel at kolabsys.com>:

[snip]

> diff --git a/release-notes.txt b/release-notes.txt
> index 5c6b599..b0a287e 100644
> --- a/release-notes.txt
> +++ b/release-notes.txt
> @@ -12,7 +12,18 @@ the 1st.README file in the package directory.
>
>  	kolab/issue4690 (Umlaut problems in system folders)
>
> -
> +    - Kolab_Storage-0.5.2-20110729
> +
> +	bugzilla.kolabsys.com #117 (Groups appear as entries in contact folders)
> +	bugzilla.kolabsys.com #135 (Add option to skip EXPUNGE command on object
> +	delete)
> +	bugzilla.kolabsys.com #137 (Folders caching issue (shutdown function))
> +	kolab/issue4466 ((Horde warning "Invalid shutdown callback" in
> +	                  Kolab/Storage/List.php)
> +	bugzilla.kolabsys.com #206 (Folder rename and caching issue)
> +	bugzilla.kolabsys.com #138 (ACL/MYRIGHTS result is not cached)
> +	bugzilla.kolabsys.com #205 (Horde_Kolab_Storage must use MYRIGHTS, not
> +	GETACL)
>

Two questions concerning the release-notes.txt format:

1) I feel we should indent multi-line entries for  
bugzilla.kolabsys.com as well. I assumed the previous entries didn't  
do that because "bugzilla.kolabsys.com #" is longer than the  
"kolab/issue" for the old tracker. So I copied the style for those  
lines for now. But I consider it harder to read - especially when both  
type of entries are present.

2) Are we going to note *all* issues that were solved in a package  
release or only those that actually affect this server flavor? For  
OpenPKG only #137, issue4466, #206 and #138 are relevant.

Thanks!

Gunnar