It is now available in source and binary form from http://dev.mysql.com/downloads/connector/net/6.3.html

The new features or changes in this release are:

• Visual Studio 2010 RTM support
• New sql editor. Create a new file with a .mysql extension to see it in action

Web browsers are taking significant steps forward to be the center of our activity when we use our computers. You may use Internet Explorer, Firefox, or Opera to send emails, write letters, do online banking, or any number of applications that used to be installed on your computer.

Web Storage Cleaning
Since all major browsers now support local storage for Web applications, CCleaner has been updated to give it the ability to clean all or portions of that local storage. The browsers themselves don’t have very good facilities for deleting the local storage, so we highly recommend that you use this feature in CCleaner.

Full change log:

• § Extended Cookie cleaning to include HTML5 Web Storage.
• § Improved Index.dat cleaning by deleting ones not locked by the system.
• § Improved “Install date” detection and accuracy for Uninstall Tool.
• § Improved file lock detection when analyzing to avoid false reporting.
• § Improved scrolling for list control to avoid repaint problems.
• § Improved cleaning of Recycle Bin.
• § Improved jumplist support to avoid possible UI lock.
• § Updated eMule cleaning.
• § Minor bug fixes.

You may download it now from piriform.com/ccleaner

For an overview of what’s new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.49 on new servers or upgrading to MySQL 5.1.49 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html

For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html

=======================================================================

C.1.2. Changes in MySQL 5.1.49 (09 July 2010)

    InnoDB Notes:

      * InnoDB Plugin has been upgraded to version 1.0.10. This
        version is considered of General Availability (GA) quality.
        InnoDB Plugin Change History
        (http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-changes.
        html), may contain information in addition to those changes
        reported here.
        In this release, the InnoDB Plugin is included in source and
        binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,
        x86_64, ia64), and generic Linux RPM packages. It also does
        not work for FreeBSD 6 and HP-UX or for Linux on generic ia64.

    Bugs fixed:

      * Replication: When using unique keys on NULL columns in
        row-based replication, the slave sometimes chose the wrong row
        when performing an update. This happened because a table
        having a unique key on such a column could have multiple rows
        containing NULL for the column used by the unique key, and the
        slave merely picked the first row containing NULL in that
        column. (Bug#53893: http://bugs.mysql.com/bug.php?id=53893)

      * Replication: FLUSH LOGS could in some circumstances crash the
        server. This occurred because the I/O thread could
        concurrently access the relay log I/O cache while another
        thread was performing the FLUSH LOGS, which closes and reopens
        the relay log and, while doing so, initializes (or
        re-initializes) its I/O cache. This could cause problems if
        some other thread (in this case, the I/O thread) is accessing
        it at the same time.
        Now the thread performing the FLUSH LOGS takes a lock on the
        relay log before actually flushing it.
        (Bug#53657: http://bugs.mysql.com/bug.php?id=53657)
        See also Bug#50364: http://bugs.mysql.com/bug.php?id=50364.

      * Replication: Two related issues involving temporary tables and
        transactions were introduced by a fix made in MySQL 5.1.37:

          1. When a temporary table was created or dropped within a
             transaction, any failed statement that following the
             CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statement
             triggered a rollback, which caused the slave diverge from
             the master.

          2. When a CREATE TEMPORARY TABLE ... SELECT * FROM ...
             statement was executed within a transaction in which only
             tables using transactional storage engines were used and
             the transaction was rolled back at the end, the
             changes---including the creation of the temporary
             table---were not written to the binary log.
        The current fix restores the correct behavior in both of these
        cases. (Bug#53560: http://bugs.mysql.com/bug.php?id=53560)
        This regression was introduced by
        Bug#43929: http://bugs.mysql.com/bug.php?id=43929.

      * Replication: When CURRENT_USER() or CURRENT_USER was used to
        supply the name and host of the affected user or of the
        definer in any of the statements DROP USER, RENAME USER,
        GRANT, REVOKE, and ALTER EVENT, the reference to
        CURRENT_USER() or CURRENT_USER was not expanded when written
        to the binary log. This resulted in CURRENT_USER() or
        CURRENT_USER being expanded to the user and host of the slave
        SQL thread on the slave, thus breaking replication. Now
        CURRENT_USER() and CURRENT_USER are expanded prior to being
        written to the binary log in such cases, so that the correct
        user and host are referenced on both the master and the slave.
        (Bug#48321: http://bugs.mysql.com/bug.php?id=48321)

      * An ALTER TABLE statement could convert an InnoDB compressed
        table (with row_format=compressed) back to an uncompressed
        table (with row_format=compact).
        (Bug#54679: http://bugs.mysql.com/bug.php?id=54679)

      * A signal-handler redefinition for SIGUSR1 was removed. The
        redefinition could cause the server to encounter a kernel
        deadlock on Solaris when there are many active threads. Other
        POSIX platforms might also be affected.
        (Bug#54667: http://bugs.mysql.com/bug.php?id=54667)

      * InnoDB could issue an incorrect message on startup, if tables
        were created under the setting innodb_file_per_table=ON and
        the server was restarted under the setting
        innodb_file_per_table=OFF. The message was of the form InnoDB:
        Warning: allocated tablespace n, old maximum was 0.
        (Bug#54658: http://bugs.mysql.com/bug.php?id=54658)

      * The make_binary_distribution target to make could fail on some
        platforms because the lines generated were too long for the
        shell. (Bug#54590: http://bugs.mysql.com/bug.php?id=54590)

      * The server failed to disregard sort order for some zero-length
        tuples, leading to an assertion failure.
        (Bug#54459: http://bugs.mysql.com/bug.php?id=54459)

      * The default value of myisam_max_extra_sort_file_size
        (http://dev.mysql.com/doc/refman/5.0/en/server-system-variable
        s.html#sysvar_myisam_max_extra_sort_file_size) could be higher
        than the maximum accepted value, leading to warnings upon the
        server start.
        (Bug#54457: http://bugs.mysql.com/bug.php?id=54457)

      * If a session tried to drop a database containing a table
        opened with HANDLER in another session, any DATABASE statement
        (CREATE, DROP, ALTER) executed by that session produced a
        deadlock. (Bug#54360: http://bugs.mysql.com/bug.php?id=54360)

      * Fast index creation could fail, leaving the new secondary
        index corrupted.
        (Bug#54330: http://bugs.mysql.com/bug.php?id=54330)

      * A client could supply data in chunks to a prepared statement
        parameter other than of type TEXT or BLOB using the
        mysql_stmt_send_long_data() C API function (or
        COM_STMT_SEND_LONG_DATA command). This led to a crash because
        other data types are not valid for long data.
        (Bug#54041: http://bugs.mysql.com/bug.php?id=54041)

      * Builds of the embedded mysqld would fail due to a missing
        element of the struct NET.
        (Bug#53908: http://bugs.mysql.com/bug.php?id=53908,
        Bug#53912: http://bugs.mysql.com/bug.php?id=53912)

      * The definition of the MY_INIT macro in my_sys.h included an
        extraneous semicolon, which could cause compilation failure.
        (Bug#53906: http://bugs.mysql.com/bug.php?id=53906)

      * A client with automatic reconnection enabled saw the error
        message Lost connection to MySQL server during query if the
        connection was lost between the mysql_stmt_prepare() and
        mysql_stmt_execute() C API functions. However,
        mysql_stmt_errno() returned 0, not the corresponding error
        number 2013.
        (Bug#53899: http://bugs.mysql.com/bug.php?id=53899)

      * Queries that used MIN() or MAX() on indexed columns could be
        optimized incorrectly.
        (Bug#53859: http://bugs.mysql.com/bug.php?id=53859)

      * The Lock_time value in the slow query log was negative for
        stored routines.
        (Bug#53191: http://bugs.mysql.com/bug.php?id=53191)

      * The results of some ORDER BY ... DESC queries were sorted
        incorrectly.
        (Bug#51431: http://bugs.mysql.com/bug.php?id=51431)

      * Index Merge between three indexes could return incorrect
        results. (Bug#50389: http://bugs.mysql.com/bug.php?id=50389)

      * Performing large numbers of RENAME TABLE statements caused
        excessive memory use.
        (Bug#47991: http://bugs.mysql.com/bug.php?id=47991)

      * The server could crash with an out of memory error when trying
        to parse a query that was too long to fit in memory. Now the
        parser rejects such queries with an ER_OUT_OF_RESOURCES error.
        (Bug#42064: http://bugs.mysql.com/bug.php?id=42064)

      * Sort-index_merge for join tables other than the first table
        used excessive memory.
        (Bug#41660: http://bugs.mysql.com/bug.php?id=41660)

      * Valgrind warnings in the InnoDB compare_record() function were
        corrected. (Bug#38999: http://bugs.mysql.com/bug.php?id=38999)

      * mysqld could fail during execution when using SSL.
        (Bug#34236: http://bugs.mysql.com/bug.php?id=34236)

      * The behavior of the RPM upgrade installation has changed.
        During an upgrade installation using the RPM packages, if the
        MySQL server is running when the upgrade occurs, the server is
        stopped, the upgrade occurs, and server is restarted. If the
        server is not already running when the RPM upgrade occurs, the
        server is not started at the end of the upgrade. The boot
        scripts for MySQL are installed in the appropriate directories
        in /etc, so the MySQL server will be restarted automatically
        at the next machine reboot.
        (Bug#27072: http://bugs.mysql.com/bug.php?id=27072)

https://www.linx.net/pubtools/trafficstats.html

https://stats.linx.net/

https://stats.linx.net/aggregate.html

The following graph shows the daily transit of between 200 and 600Gbps

• File size masks are allowed in script commands.
• Conversion of timestamps between local and remote systems with respect to DST follows changes introduced in Windows 7.
• Installation package includes development versions of PuTTYgen and Pageant applications. It brings following changes:
  • PuTTYgen supports importing of new-style OpenSSH private keys (encrypted by AES rather than 3DES).
  Advertisements:
• SSH core upgraded to the latest development snapshot of PuTTY (2010-05-19, revision 8952). Improving GSSAPI support.
• Script commands and output are included into session log.
• Bug fix: IPv6 support was broken.
• Bug fix: Protocol ftps was ignored in session URL when port number was also specified.
• Bug fix: Suggested session path was duplicated when saving new session.
• Bug fix: SFTP packet counter overflow.
• Bug fix: Sorting by owner/group was broken.
• Bug fix: Failure when opening session protected with master password from command-line in console.
• Bug fix: Saving password in default session settings did not force prompt for master password, allowing the password being stored unecrypted.
• Bug fix: Missing OpenCandy DLL on Windows startup.
• Bug fix: Hangs when changing directory using directory tree after toggling showing of hidden files.
• Bug fix: !.! was suggested as name of executable when browsing for previously undefined executable.
• Bug fix: Failure when running multiple instances of console interface tool in parallel.

The “-m3″ suffix indicates that these releases belong to the third milestone, also called “Celosia”.

You can read more about the release model and the planned milestones at  http://forge.mysql.com/wiki/Development_Cycle

The new features in these releases are of beta quality. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.

Please note that *downgrading* from these releases to a previous release series, including MySQL Server 5.5 milestone 2 (Betony) releases, is not supported.

MySQL 5.5 is based on MySQL 5.4, which won’t get any further updates.

MySQL 5.5 includes several high-impact changes to address scalability and performance issues in MySQL Server. These changes exploit advances in hardware and CPU design and enable better utilization of existing

hardware.

For an overview of what’s new in MySQL 5.5, please see the section “What Is New in MySQL 5.5″ online at  http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html

For information on installing MySQL 5.5.5-m3 on new servers, please see the MySQL installation documentation at  http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important upgrade considerations at

http://dev.mysql.com/doc/refman/5.5/en/upgrading-from-previous-series.html <http://dev.mysql.com/doc/refman/5.5/en/installing.html>

MySQL Server 5.5 is available in source and binary form for a number of platforms from the “Development Releases” selection of download pages at

http://dev.mysql.com/downloads/mysql/

The complete list of all “Bugs Fixed” may be viewed online at  http://dev.mysql.com/doc/refman/5.5/en/news-5-5-5.html

Special note for those of you who build from source:

In MySQL 5.5.5-m3, CMake joins GNU autotools as a build framework for all platforms. Existing support for GNU autotools isn’t going away just yet, but if you are so inclined, you can now alternatively use CMake as per the

instructions on the web page linked below. The official packages for this release are the first to be produced using CMake.

http://forge.mysql.com/wiki/CMake

Changes in MySQL 5.5.5:

|InnoDB is now the default storage engine, rather than MyISAM in|||  the regular versions of MySQL. This change has the following consequences:

* Existing tables are not affected by this change, only new tables that are created.

* Some of the|InnoDB|  option settings also change, so that the default configuration represents the best practices for|InnoDB|

functionality,reliability, and file management:

|innodb_file_format=Barracuda|  rather than|Antelope|,

|innodb_strict_mode=TRUE|  rather than|FALSE|, and

|innodb_file_per_table=TRUE|  rather than|FALSE|.

* The system tables remain in|MyISAM|  format.

*|MyISAM|  remains the default storage engine for the embedded version of MySQL

Bugs Fixed:

* Performance: While looking for the shortest index for a covering index scan, the optimizer did not consider the full

row length for a clustered primary key, as in InnoDB. Secondary covering indexes will now be preferred, making full

table scans less likely.

(Bug#39653:http://bugs.mysql.com/bug.php?id=39653)

* Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and

compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges

and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST.

In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field

definitions of any table in all other databases and potentially of other MySQL instances accessible from the

server’s file system.

Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one

table could delete or read content from any other table in all databases on this server, and potentially of other MySQL

instances accessible from the server’s file system.

(Bug#53371:http://bugs.mysql.com/bug.php?id=53371,

CVE-2010-1848 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1848))

* Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the

table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown,

which could be exploited by an authenticated user to inject malicious code.

(Bug#53237:http://bugs.mysql.com/bug.php?id=53237,

CVE-2010-1850 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1850))

* Security Fix: Privilege checking for UNINSTALL PLUGIN was incorrect. (Bug#51770:http://bugs.mysql.com/bug.php?id=51770,

CVE-2010-1621 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1621))

* Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum

size of one packet.

(Bug#50974:http://bugs.mysql.com/bug.php?id=50974,

CVE-2010-1849 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1849))

* Incompatible Change: TRUNCATE TABLE did not take an exclusive lock on a table if truncation was done by deleting all rows in

the table. For InnoDB tables, this could break proper isolation because InnoDB ended up aborting some granted locks

when truncating a table. Now an exclusive metadata lock is taken before TRUNCATE TABLE can proceed. This guarantees that

no other transaction is using the table.

Incompatible change: Truncation using delete no longer fails if sql_safe_updates is enabled (this was an undocumented side

effect). (Bug#42643:http://bugs.mysql.com/bug.php?id=42643)

* Important Change: Replication: It was possible to set sql_log_bin with session scope inside a transaction or

subquery. (Bug#53437:http://bugs.mysql.com/bug.php?id=53437)

* Important Change: Replication: When changing binlog_format or binlog_direct_non_transactional_updates, permissions were not

checked prior to checking the scope and context of the variable being changed.

As a result of this fix, an error is no longer reported when—in the context of a transaction or a stored

function—you try to set a value for a session variable that is the same as its previous value, or for a variable whose

scope is global only.

(Bug#51277:http://bugs.mysql.com/bug.php?id=51277)

* Important Change: Replication: When invoked, CHANGE MASTER TO and SET GLOBAL sql_slave_skip_counter now cause information to

be written to the error log about the slave’s state prior to execution of the statement. For CHANGE MASTER TO, this

information includes the previous values for MASTER_HOST, MASTER_PORT, MASTER_LOG_FILE, and MASTER_LOG_POS. For SET

GLOBAL sql_slave_skip_counter, this information includes the previous values of sql_slave_skip_counter, the group relay log

name, and the group relay log position.

(Bug#43406:http://bugs.mysql.com/bug.php?id=43406,

Bug#43407:http://bugs.mysql.com/bug.php?id=43407)

* Partitioning: Replication: Attempting to execute LOAD DATA on a partitioned MyISAM table while using statement-based logging

mode caused the master to hang or crash.

(Bug#51851:http://bugs.mysql.com/bug.php?id=51851)

* Partitioning: Replication: The NO_DIR_IN_CREATE server SQL mode was not enforced when defining subpartitions. In certain

cases, this could lead to failures on replication slaves.

(Bug#42954:http://bugs.mysql.com/bug.php?id=42954)

* Partitioning: Rows inserted into a table created using a PARTITION BY LIST COLUMNS option referencing multiple columns

could be inserted into the wrong partition.

(Bug#52815:http://bugs.mysql.com/bug.php?id=52815)

* Partitioning: Partition pruning on RANGE partitioned tables did not always work correctly; the last partition was not

excluded if the range was beyond it (when not using MAXVALUE).

Now the last partition is not included if the partitioning function value is not within the range.

(Bug#51830:http://bugs.mysql.com/bug.php?id=51830)

* Partitioning: Attempting to partition a table using a DECIMAL column caused the server to crash; this not supported and is

now specifically disallowed.

Bug#51347:http://bugs.mysql.com/bug.php?id=51347)

* Partitioning: ALTER TABLE statements that cause table partitions to be renamed or dropped (such as ALTER TABLE …

ADD PARTITION, ALTER TABLE … DROP PARTITION, and ALTER TABLE … REORGANIZE PARTITION) — when run concurrently with

queries against the INFORMATION_SCHEMA.PARTITIONS table —

could fail, cause the affected partitioned tables to become unusable, or both. This was due to the fact that the

INFORMATION_SCHEMA database ignored the name lock imposed by the ALTER TABLE statement on the partitions affected. In

particular, this led to problems with InnoDB tables, because InnoDB would accept the rename operation, but put it in a

background queue, so that subsequent rename operations failed when InnoDB was unable to find the correct partition. Now,

INFORMATION_SCHEMA honors name locks imposed by ongoing ALTER TABLE statements that cause partitions to be renamed or

dropped. (Bug#50561:http://bugs.mysql.com/bug.php?id=50561)

See also Bug#47343:http://bugs.mysql.com/bug.php?id=47343,

Bug#45808:http://bugs.mysql.com/bug.php?id=45808.

* Partitioning: The insert_id server system variable was not reset following an insert that failed on a partitioned MyISAM

table having an AUTO_INCREMENT column.

(Bug#50392:http://bugs.mysql.com/bug.php?id=50392)

* Partitioning: Foreign keys are not supported on partitioned tables. However, it was possible via an ALTER TABLE statement

to set a foreign key on a partitioned table; it was also possible to partition a table with a single foreign key.

(Bug#50104:http://bugs.mysql.com/bug.php?id=50104)

* Partitioning: When attempting to perform DDL on a partitioned table and the table’s .par file could not be found, the server

returned the inaccurate error message Out of memory; restart server and try again (needed 2 bytes). Now in such cases, the

server returns the error Failed to initialize partitions from .par file. (Bug#49161:http://bugs.mysql.com/bug.php?id=49161)

* Partitioning: GROUP BY queries performed poorly for some partitioned tables. This was due to the block size not being

set for partitioned tables, thus the keys per block was not correct, which could cause such queries to be optimized

incorrectly.

(Bug#48229:http://bugs.mysql.com/bug.php?id=48229)

See also Bug#37252:http://bugs.mysql.com/bug.php?id=37252.

* Partitioning: REPAIR TABLE failed for partitioned ARCHIVE tables. (Bug#46565:http://bugs.mysql.com/bug.php?id=46565)

* Replication: When using unique keys on NULL columns in row-based replication, the slave sometimes chose the wrong row

when performing an update. This happened because a table having a unique key on such a column could have multiple rows

containing NULL for the column used by the unique key, and the slave merely picked the first row containing NULL in that

column. (Bug#53893:http://bugs.mysql.com/bug.php?id=53893)

* Replication: When a CREATE TEMPORARY TABLE … SELECT statement was executed within a transaction that updated only

transactional engines and was later rolled back (for example, due to a deadlock) the changes—including the creation of the

temporary table—were not written to the binary log, which caused subsequent updates to this table to fail on the slave.

(Bug#53421:http://bugs.mysql.com/bug.php?id=53421)

* Replication: When using the statement-based logging format, statements that used CONNECTION_ID() were always kept in the

transaction cache; consequently, nontransactional changes that should have been flushed before the transaction were kept in

the transaction cache.

(Bug#53075:http://bugs.mysql.com/bug.php?id=53075)

This regression was introduced by

Bug#51894:http://bugs.mysql.com/bug.php?id=51894.

* Replication: In some cases, attempting to update a column with a value of an incompatible type resulted in a mismatch between

master and slave because the column value was set to its implicit default value on the master (as expected), but the

same column on the slave was set to NULL.

(Bug#52868:http://bugs.mysql.com/bug.php?id=52868)

* Replication: When temporary tables were in use, switching the binary logging format from STATEMENT to ROW did not take

effect until all temporary tables were dropped. (The existence of temporary tables should prevent switching the format only

from ROW to STATEMENT from taking effect, not the reverse.)

(Bug#52616:http://bugs.mysql.com/bug.php?id=52616)

* Replication: A buffer overrun in the handling of DATE column values could cause mysqlbinlog to fail when reading back logs

containing certain combinations of DML on a table having a DATE column followed by dropping the table.

(Bug#52202:http://bugs.mysql.com/bug.php?id=52202)

* Replication: The failure of a REVOKE statement was logged with the wrong error code, causing replication slaves to stop even

when the failure was expected on the master.

(Bug#51987:http://bugs.mysql.com/bug.php?id=51987)

* -laio missing from embedded libs (Bug#55215:_http://bugs.mysql.com/bug.php?id=55215_)

Please see the complete list of changes to MySQL 5.5.5 at http://dev.mysql.com/doc/refman/5.5/en/news-5-5-5.html

What’s New in this Beta version of Thunderbird 3.1

There were several fixes to improve stability and security of Thunderbird 3.1. There were also fixes to the user interface and attachment handling. Please see the complete list of changes in this version or view the release notes for more information.

What’s New in Thunderbird 3.1

We hope you enjoy the new features in Thunderbird. We have new search tools, tabbed email, message archiving, and hundreds of add-ons to make Thunderbird 3.1 all yours.

Easier to Upgrade with New Migration Assistant

Under the Help Menu, select the Migration Assistant to help you change your Toolbar layout and add features like Compact Header and Advanced Folder Columns.

Better Search with New Search Tools

The new Quick Filter Toolbar lets you filter your email faster. Filter your email by New Messages, Tags, people in your Address Book, or using search terms. You can also “Pin” or save a Filter and use it across multiple folders.

Type in your search term in the Global Search Bar and we will open your search results in a new tab. You can pinpoint what you’re looking for with Thunderbird’s filtering and timeline tools.

Tabbed Email

If you like Firefox’s tabbed browsing, you’re going to love tabbed email. Double-click or hit enter on a mail message to open messages in a new tab window. You can right-click on messages or folders to open them in a tab background.

Message Archiving

Clicking the Archive button or the ‘A’ key will archive your email. Archiving mail moves email from your inbox into the new archive folder system.

Personal Calendar

With help of the Lightning Add-on, you can now organize your appointments and tasks from within Thunderbird. Aside from storing your calendar on this computer, you can also subscribe to network calendars so you don’t miss a minute, even on the go.

More New Features to Explore:

• Unified Folders
• Activity Manager
• One-click Address Book
• Attachment Reminder
• Hundreds of new Add-ons to try

For additional product information, visit the Thunderbird Home Page.

Following the consultation the new .uk policy development process has been launched.  The new process has an open approach to developing policy for.uk, that focuses on specific issues. Each issue will be dealt with in specially convened Issue Groups that ensure the right stakeholders are involved in the development of policy that is relevant to them.

Full details about the new process and how you can get involved are available here: http://www.nominet.org.uk/policy/

MySQL Workbench should be your preferred tool for Design, Development, and Administration of your MySQL database applications.

MySQL Workbench 5.2 GA provides:

• Data Modeling

• Query (replaces the old MySQL Query Browser)

• Administration (replaces the old MySQL Administrator)

It can be downloaded from:  http://dev.mysql.com/downloads/workbench/

Workbench Documentation and details on changes between releases can be found on these pages

http://dev.mysql.com/doc/workbench/en/index.html

http://dev.mysql.com/doc/workbench/en/wb-change-history.html