First of all let me say thanks to the community and coreteam for being on the

Nr. 4 attempt and don't tell me I don't trie hard enough. I feel like a complete a*&%, but get a feeling there's some automated censorship going on in this forum looking for banned words like "a_l_e_r_t?" Just let me retry rephrasing that (absurd situation btw or at least publish a list of banned words if you don't mind):

First of all let me say thanks to the community and coreteam for being on the [beep] for security flaws and coming up with a solution so quickly. Secondly after reading the reminder on some new options to run the upgrade proces more efficiently (blog C.Nurse), I would like to ask the following i.e. make a suggestion.

- as probably many other DNN users/ developers do, once the core framework is installed you start tweaking/ rewriting/ redesigning the site. Not just by way of skins/ containers/ css files, but on different levels of the installation (aspx files etc, if necessary) to get it fully customized.

- of course you keep note of these changes, document them carefully, because experience learns that on any new DNN upgrade, you have to go through the tedious process of getting those changes back in place after running the upgrade or (as an alternative way) remove as many files from the upgrade package beforehand that
do not contain any core changes but might undo some customizations.

- one other reason for cleaning the upgrade package beforehand is to size it down as much as possible to speed up the ftp proces. Why would you re-upload a Documentation directory you removed in the first place. Or reupload 1.69 Mb of perfectly unchanged images, default skins, containers etc. etc. I guess you understand how timeconsuming all this can be.

Question therefore is:

1 Wouldn't it be possible to create an upgrade package that contains no more than
a. new and changed files;
b. absolute bare minimum files to keep the core stable and in tune with the changes (ie. dll's) and the install files for the upgrade;

2 Or (and maybe it's there already, but i havent found it yet) on every upgrade publish a list of files changed and affected in the new version. We have gemini of course for a general description of changes but it would certainly help to get a more technical list of changes (filenames, codechanges even?).

Do theses questions/ suggestions make sense at all? Looking forward to your reactions.

When we had started, the DNN use to come only in one flavour, i.e. the single zip file (what is named "source version" now)

Now we have Source and Install versions and also the upgrade version.

May be, we can have one more such version, let say, Upggrade From x.yy.zz version (most likely that would be the last version, for those, who regualry update the DNN installations)