If non installable profiles (really: hidden profiles) have been
installed in GS, mark their products as installed in the QI. This
does not work when also that product is marked as non installable,
because in normal operation (outside of plone.app.upgrade) this does
not happen either.
[maurits]

Unmark installed profiles that are no longer available.
[maurits]

Fixes:

Fixed removal of Large Plone Folder when migrating from Plone 3.
[maurits]

1.1.3 (2011-10-08)

1.1.2 (2011-09-22)

1.1.1 (2011-09-21)

Fix v41.alphas.convert_to_uuidindex() to truly ignore acquired
UID values in the index instead of accidentally treating them
as duplicates, due to a bug in path comparison. Fixes for
cases where multiple items without UID() method are contained
in a folder with a UID in a site being upgraded to 4.1:
http://dev.plone.org/plone/ticket/12185

Modify the restoreTheme upgrade step to improve handling of themes when
upgrading from Plone 3. Now if the skin was “Plone Default”, it will be
set to “Plone Classic Theme” if the layers were uncustomized. If the
layers were customized, the layers and viewlet settings will be copied to
a new skin called “Old Plone 3 Custom Theme”, and then “Plone Default”
will be reset to its typical configuration in a fresh Plone 4 site.
This closes http://dev.plone.org/plone/ticket/10399
[davisagli]

Add upgrade step to remove the Large Plone Folder type for Plone 4.0rc1
(there is another step which already turns Large Plone Folders into
unordered regular Folders). Removed references to Large Plone Folder from
old upgrade steps.
[davisagli]

Enable the diff export in functional upgrade tests, we do a complete
GenericSetup export of all upgraded sites now.
[hannosch]

Remove the hint of doing an export/import comparison for the full upgrades.
These have varying add-ons installed depending on the original site and its
quite hard to get the same add-ons installed again in a new site.
[hannosch]

Added functional upgrade tests based on an actual zexp export of each major
version of Plone. Each one is imported and upgraded. A diff of the upgraded
configuration vs the one of a completely new site is generated. Thanks to
CMF for the inspiration. This closes http://dev.plone.org/plone/ticket/721.
[hannosch]

Declared missing dependencies.
[hannosch]

1.0a3 - 2009-12-16

Updated all profile versions in the Plone 4 series to new simple integer
based numbers.
[hannosch]

1.0a2 - 2009-12-02

Recompile all persistent Python Scripts during the upgrade.
[hannosch]

Simplify installation of new dependencies and include plone.app.imaging.
[hannosch]

Run the steps found in the Products.CMFPlone:dependencies profile.
[hannosch]

Remove calendarpopup.js from portal_javascripts.
[hannosch]

Preserve the default theme after an upgrade instead of making sunburst the
new default. Also ensure the classic_styles layer isn’t part of sunburst.
[hannosch]

The plone_styles layer is automatically renamed to classic_styles.
[hannosch]

Let the mailhost upgrade step replace broken objects with a fresh standard
mailhost. It’s likely our new one has the features of the custom product.
[hannosch]

Clean up Zope’s product registry to deal with removed products and internal
changes to the HelpSys catalogs.
[hannosch]

Deal with more removed import steps and remove them from the registry.
[hannosch]

Cleanup the skins tools and remove broken directory views as well as cleaning
up the skin selections to avoid references to no longer existing directories.
[hannosch]

Remove entries from the toolset registry pointing to no longer existing
tools. This can happen when add-ons have been uninstalled.
[hannosch]

When upgrading to Plone 4.0a1, be sure to update the toolset with new class
locations before importing any other profiles, which might otherwise fail
in the toolset step. Be sure to update the locations for the tools which
moved from CMFPlone to PlonePAS, for upgrades from very old sites.
[davisagli]