modules/update_status/CHANGELOG.txt

Update Status 5.x-2.1
  o #178892 by webchick: Use an API function to get the private key.
  o #184900 by webernet: Fixed bug where email wasn't getting sent in
    some cases when it should have been.
  o #196775 by dww: Fixed a bug that caused truncated error messages to
    be displayed when the site is running an insecure version of core.
  o #197186 by dww: Backport of major update.module patch from D6 core:
    - Fixed bug where update_status would not warn sites when a
      currently installed release or an entire project being used has
      been unpublished.
    - Added support for project maintainers that want to support
      multiple major versions (branches) for one version of core.
    - Added support for flagging both individual releases and projects
      as "unsupported" or "insecure", to pave the way for new
      workflows (instead of just unpublishing things) for the Drupal
      security team and project maintainers.
    - Reorganized and simplified some code to avoid duplication and
      needless complications.
  o #208687 by dww: Fixed major bug that printed bogus results and
    recommended that users downgrade to an older version when a site
    upgraded a module or Drupal core but did not manually refresh the
    available update data. Now, before using the cached available
    update data, the code ensures that none of the .info files have
    been changed since the last time it fetched data.
  o #158526 by dww: Changed the hook_version_alter() API exposed by
    update_status to be hook_system_info_alter() so that all
    attributes in the .info files can be altered. This API change is
    required to fix some bugs in the http://drupal.org/cvs_deploy
    module, which is the only known user of this API.
  o #200028 by agentrickard, dww: Significantly enhanced performance
    of the admin/* pages by adding DB caching for the list of
    installed modules and their current status. The cache is cleared
    every time new available release data is fetched, every time the
    admin visits the modules page, status report, or available updates
    report, or every hour if nothing else clears it before that.


Update Status 5.x-2.0
  o #165695: Added another database update to completely rebuild the menu
    since the "Check manually" path moved to "admin/logs/updates/check".
  o #165638: Improved usability for the "Check manually" link on the
    update report by wrapping it in () and adding some padding.
  o #155483: Simplified the description of the email notification setting.
  o #155878: Re-use the same t() string for both the watchdog() and
    drupal_set_message() when fetching information about available updates.
  o Added or updated translations:
    - Czech (cs)
    - German (de)
    - Greek (el)
    - Hungarian (hu)
    - Italian (it)
    - Norwegian (nb)


Update Status 5.x-2.0-rc2
  o #155483: Backported numerous improvements from update.module in 6.x core:
  == General ==
    - The module now nags site administrators on admin/* if the site is
      missing a security update.
    - Added a drupal_set_message() when fetching data manually (success
      or failure) and cleaned up wording of watchdog().
    - Added watchdog() error message when you can't fetch any data.
    - The menu callback for manually checking is now at 
      'admin/logs/updates/check'.
    - Lots of internal improvements to the code to improve clarity.
  == Available updates report ==
    - Used format_interval() for the "Last checked:" date and time.
    - Removed the "Ignored" part whenever a row on the update report is
      yellow, except for when something is ignored because of the settings.
    - Changed the wording when the "Notification threshold" is set to
      "Only security updates", and you have a non-security update
       available. Now, it just says "Update available".
    - Added support for a variable to override the default fetch URL.
  == Settings page ==
    - Moved the email notification setting to the top of the page.
    - Renamed "Error threshold" to "Notification threshold" and improved
      the description. 
    - Fixed t() bug in form_set_error() during email validation.
    - Removed the setting to opt out of the usage reporting.  No one
      who's willing to run this module in the first place could
      possibly complain about the random string appended as a query arg
      on the fetch URL, and the extra setting needlessly complicates
      the settings page.
  o Fixed a notice on the status report page when the available update
    cache is empty: we were generating a 1/2 constructed line for core
    and a full line for contrib.  Now, if the cache is empty, we just
    generate the warning line for core and nothing for contrib.
  o Fixed minor bug: the status report text was missing a space.
  o Fixed bug caused by variable name typo: $base_util vs. $base_url.
  o Made the status report table all 100% wide for a more consistent UI.
  o #155281: Use flexible path for serving/fetching release history.
  o #155428: Removed the human-readable menu path from the notification
    email since it was considered a burden to translate.
  o Added an implementation of hook_uninstall() to purge variables.
    It's important that when sites running this want to upgrade to 6.x
    core that they first uninstall this module, or they'll be left with
    stale variables.
  o Updated README.txt to reflect recent changes and to mention
    uninstalling the module before upgrading to 6.x core.


Update Status 5.x-2.0-rc
  o #124715: Added setting for email notifications when updates are available.
  o #154868: Fixed bugs and inconsistencies with security update warnings.
  o #153757: Renamed the "Warning threshold" setting to "Error threshold".
  o #149079: A few CSS tweaks and fixes for recommended version:
    - Renamed the CSS class to "version-recommended-strong" to indicate
      it's the strongly recommended version among many (the old name,
      "version-recommended-not-latest" isn't good since "Latest" isn't
      the only possible thing we're distinguishing against).
    - Fixed classes so that if we're recommending a security release,
      it gets the subtle "zebra" stripe, too.
  o #154689: Restored the CSS classes on the per-project settings table,
    (and made them consistent across all rows), but made them more
    specific to avoid name conflicts.
  o Fixed minor glitch in the logic for when to display the
    'Development version'.
  o Fixed bug in hook_version_alter() invocation for CVS deploy
    integration (http://drupal.org/project/cvs_deploy).
  o Updated screenshot to show off recent UI and functionality improvements.

Update Status 5.x-2.0-beta2
  == Bug fixes ==
  o #153756: Fixed math bug when comparing the timestamps of dev snapshots.
  o #153798: Fixed warning logic for development snapshots and flag
    security updates.
  o #153502: Made update_status E_ALL compliant.
  o #154540: Minor wording fixes for the UI and help texts.
  o #153569: Fixed obscure CSS problem for Firefox 2.0.0.4 on Windows XP.
  o #154689: Fixed settings page bug in marvin theme due to CSS class conflict.
  o Don't clear the update_status cache when an admin saves the system
    themes page, since in 5.x, there is no information about theme updates.
  == New features and enhancements ==
  o #153741: Added support for optionally reporting anonymous usage statistics.
  o #153757: Added a setting to only warn when there are security updates.
  o #154049: Added a setting to control how frequently to check for updates.
  o #146564: Major performance gain for fetching available update data:
    directly fetch the .xml files instead of going through the Drupal menu
    callback inside project_release.module.
  o #153783: Don't hard-code dark black (#000) in update_status.css, use
    theme's default foreground color.
  o #149079: Further visual clarity about the recommended version: use a
    subtle "zebra stripe" with a slightly lighter shade of the status
    color for the entire recommended version line.
  o Completely re-wrote the README to match 5.x-2.* reality.

Update Status 5.x-2.0-beta
  o Major re-write to use a whole new system for finding available updates.
  o Lots of improvements to the user interface and internals of the code.
  o #125742: The status report indicates updates involving security issues.
  o #149918: Add support for "Also available" entries in the status report.
  o #150316: All CVS-specific code has been moved into the CVS Deploy module:
      http://drupal.org/project/cvs_deploy
  o #144694: Available update data now stored in the {cache} table instead
      of the {variables} table for better performance and functionality.
  o #149921: Clear update_status cache when you enable/disable modules.
  o #145095: Core modules were not always considered part of Drupal core.
  o #141507: Fixed bug in the links to manually run cron to find updates.
  o #151734: Display the administrator's note when a project is
      ignored due to the settings.
  o #149079: Highlight the 'Recommended' version if there are other
      things listed ('Latest version', 'Also available', etc).

Update Status 5.x-1.2
  Fixed broken notify on administer and status pages.

Update Status 5.x-1.1
  o #123100: Provide a graceful error message and exit if 'gzinflate' cannot be found.
  o Attempt to guess at the project and version for projects checked out of CVS.
  o #131049: (by Senpai) Fix for CSS to ensure the font color is visible with our backgrounds.
  o #124377: Add a link to the release notes.
  o #125489: Include date with available version.
  o #124440 and #126298: Settings page, set to check or not, and notes to remind yourself why.

Update Status 5.x-1.0
  Initial release
1	Update Status 5.x-2.1
2	o #178892 by webchick: Use an API function to get the private key.
3	o #184900 by webernet: Fixed bug where email wasn't getting sent in
4	some cases when it should have been.
5	o #196775 by dww: Fixed a bug that caused truncated error messages to
6	be displayed when the site is running an insecure version of core.
7	o #197186 by dww: Backport of major update.module patch from D6 core:
8	- Fixed bug where update_status would not warn sites when a
9	currently installed release or an entire project being used has
10	been unpublished.
11	- Added support for project maintainers that want to support
12	multiple major versions (branches) for one version of core.
13	- Added support for flagging both individual releases and projects
14	as "unsupported" or "insecure", to pave the way for new
15	workflows (instead of just unpublishing things) for the Drupal
16	security team and project maintainers.
17	- Reorganized and simplified some code to avoid duplication and
18	needless complications.
19	o #208687 by dww: Fixed major bug that printed bogus results and
20	recommended that users downgrade to an older version when a site
21	upgraded a module or Drupal core but did not manually refresh the
22	available update data. Now, before using the cached available
23	update data, the code ensures that none of the .info files have
24	been changed since the last time it fetched data.
25	o #158526 by dww: Changed the hook_version_alter() API exposed by
26	update_status to be hook_system_info_alter() so that all
27	attributes in the .info files can be altered. This API change is
28	required to fix some bugs in the http://drupal.org/cvs_deploy
29	module, which is the only known user of this API.
30	o #200028 by agentrickard, dww: Significantly enhanced performance
31	of the admin/* pages by adding DB caching for the list of
32	installed modules and their current status. The cache is cleared
33	every time new available release data is fetched, every time the
34	admin visits the modules page, status report, or available updates
35	report, or every hour if nothing else clears it before that.
36
37
38	Update Status 5.x-2.0
39	o #165695: Added another database update to completely rebuild the menu
40	since the "Check manually" path moved to "admin/logs/updates/check".
41	o #165638: Improved usability for the "Check manually" link on the
42	update report by wrapping it in () and adding some padding.
43	o #155483: Simplified the description of the email notification setting.
44	o #155878: Re-use the same t() string for both the watchdog() and
45	drupal_set_message() when fetching information about available updates.
46	o Added or updated translations:
47	- Czech (cs)
48	- German (de)
49	- Greek (el)
50	- Hungarian (hu)
51	- Italian (it)
52	- Norwegian (nb)
53
54
55	Update Status 5.x-2.0-rc2
56	o #155483: Backported numerous improvements from update.module in 6.x core:
57	== General ==
58	- The module now nags site administrators on admin/* if the site is
59	missing a security update.
60	- Added a drupal_set_message() when fetching data manually (success
61	or failure) and cleaned up wording of watchdog().
62	- Added watchdog() error message when you can't fetch any data.
63	- The menu callback for manually checking is now at
64	'admin/logs/updates/check'.
65	- Lots of internal improvements to the code to improve clarity.
66	== Available updates report ==
67	- Used format_interval() for the "Last checked:" date and time.
68	- Removed the "Ignored" part whenever a row on the update report is
69	yellow, except for when something is ignored because of the settings.
70	- Changed the wording when the "Notification threshold" is set to
71	"Only security updates", and you have a non-security update
72	available. Now, it just says "Update available".
73	- Added support for a variable to override the default fetch URL.
74	== Settings page ==
75	- Moved the email notification setting to the top of the page.
76	- Renamed "Error threshold" to "Notification threshold" and improved
77	the description.
78	- Fixed t() bug in form_set_error() during email validation.
79	- Removed the setting to opt out of the usage reporting. No one
80	who's willing to run this module in the first place could
81	possibly complain about the random string appended as a query arg
82	on the fetch URL, and the extra setting needlessly complicates
83	the settings page.
84	o Fixed a notice on the status report page when the available update
85	cache is empty: we were generating a 1/2 constructed line for core
86	and a full line for contrib. Now, if the cache is empty, we just
87	generate the warning line for core and nothing for contrib.
88	o Fixed minor bug: the status report text was missing a space.
89	o Fixed bug caused by variable name typo: $base_util vs. $base_url.
90	o Made the status report table all 100% wide for a more consistent UI.
91	o #155281: Use flexible path for serving/fetching release history.
92	o #155428: Removed the human-readable menu path from the notification
93	email since it was considered a burden to translate.
94	o Added an implementation of hook_uninstall() to purge variables.
95	It's important that when sites running this want to upgrade to 6.x
96	core that they first uninstall this module, or they'll be left with
97	stale variables.
98	o Updated README.txt to reflect recent changes and to mention
99	uninstalling the module before upgrading to 6.x core.
100
101
102	Update Status 5.x-2.0-rc
103	o #124715: Added setting for email notifications when updates are available.
104	o #154868: Fixed bugs and inconsistencies with security update warnings.
105	o #153757: Renamed the "Warning threshold" setting to "Error threshold".
106	o #149079: A few CSS tweaks and fixes for recommended version:
107	- Renamed the CSS class to "version-recommended-strong" to indicate
108	it's the strongly recommended version among many (the old name,
109	"version-recommended-not-latest" isn't good since "Latest" isn't
110	the only possible thing we're distinguishing against).
111	- Fixed classes so that if we're recommending a security release,
112	it gets the subtle "zebra" stripe, too.
113	o #154689: Restored the CSS classes on the per-project settings table,
114	(and made them consistent across all rows), but made them more
115	specific to avoid name conflicts.
116	o Fixed minor glitch in the logic for when to display the
117	'Development version'.
118	o Fixed bug in hook_version_alter() invocation for CVS deploy
119	integration (http://drupal.org/project/cvs_deploy).
120	o Updated screenshot to show off recent UI and functionality improvements.
121
122	Update Status 5.x-2.0-beta2
123	== Bug fixes ==
124	o #153756: Fixed math bug when comparing the timestamps of dev snapshots.
125	o #153798: Fixed warning logic for development snapshots and flag
126	security updates.
127	o #153502: Made update_status E_ALL compliant.
128	o #154540: Minor wording fixes for the UI and help texts.
129	o #153569: Fixed obscure CSS problem for Firefox 2.0.0.4 on Windows XP.
130	o #154689: Fixed settings page bug in marvin theme due to CSS class conflict.
131	o Don't clear the update_status cache when an admin saves the system
132	themes page, since in 5.x, there is no information about theme updates.
133	== New features and enhancements ==
134	o #153741: Added support for optionally reporting anonymous usage statistics.
135	o #153757: Added a setting to only warn when there are security updates.
136	o #154049: Added a setting to control how frequently to check for updates.
137	o #146564: Major performance gain for fetching available update data:
138	directly fetch the .xml files instead of going through the Drupal menu
139	callback inside project_release.module.
140	o #153783: Don't hard-code dark black (#000) in update_status.css, use
141	theme's default foreground color.
142	o #149079: Further visual clarity about the recommended version: use a
143	subtle "zebra stripe" with a slightly lighter shade of the status
144	color for the entire recommended version line.
145	o Completely re-wrote the README to match 5.x-2.* reality.
146
147	Update Status 5.x-2.0-beta
148	o Major re-write to use a whole new system for finding available updates.
149	o Lots of improvements to the user interface and internals of the code.
150	o #125742: The status report indicates updates involving security issues.
151	o #149918: Add support for "Also available" entries in the status report.
152	o #150316: All CVS-specific code has been moved into the CVS Deploy module:
153	http://drupal.org/project/cvs_deploy
154	o #144694: Available update data now stored in the {cache} table instead
155	of the {variables} table for better performance and functionality.
156	o #149921: Clear update_status cache when you enable/disable modules.
157	o #145095: Core modules were not always considered part of Drupal core.
158	o #141507: Fixed bug in the links to manually run cron to find updates.
159	o #151734: Display the administrator's note when a project is
160	ignored due to the settings.
161	o #149079: Highlight the 'Recommended' version if there are other
162	things listed ('Latest version', 'Also available', etc).
163
164	Update Status 5.x-1.2
165	Fixed broken notify on administer and status pages.
166
167	Update Status 5.x-1.1
168	o #123100: Provide a graceful error message and exit if 'gzinflate' cannot be found.
169	o Attempt to guess at the project and version for projects checked out of CVS.
170	o #131049: (by Senpai) Fix for CSS to ensure the font color is visible with our backgrounds.
171	o #124377: Add a link to the release notes.
172	o #125489: Include date with available version.
173	o #124440 and #126298: Settings page, set to check or not, and notes to remind yourself why.
174
175	Update Status 5.x-1.0
176	Initial release