[dokuwiki-teams] Re: [release-team] Deprecation list

> we have be talking about making deprecation more formal and I tried to add
> a table in http://www.dokuwiki.org/devel:release_plan?&#deprecation
> But I'm not satisfied with the result, any better ideas?

Even if it's not 100% optimized, it's a first step which we can improve
in the future. 
I would add a column which hold's information (if they exists) about 
significant impacts on DW or installed (only the popular ones) plugins. 
(Like I had with Anteater and the out-dated translation plugin.)

> Today the public changlog are made manually mostly from memory.
> http://www.dokuwiki.org/changes

I just had a talk about the changes page with my colleague today.
He wanted to publish the new features and changes in our
company's wiki. But as a normal user w/o being involved in
the DW development, you only have some "wtf's" in mind after
reading the changes section. 
The most of the written changes have to be put more in end-user
instead of the currently existing developer context. 
To bring this forward, I'll create first an appropriate German 
translation and adopt it in a second step to English.

My opinion is, that the user will only upgrade do newer releases,
if it's clear what advantages they have after upgrading. If they don't
understand the changelog there's no need to upgrade.

Other related posts: