Hi all



We are pleased to inform you that Mingle 3.5 is now generally available.

What's New in Mingle 3.5?

Multi-Dimensional Card Wall enhancements

Building on the features we added in Mingle 3.4, Mingle's Grid View now allows you to create and add a card to your Multi-Dimensional Card Walls with a simple drag and drop. The ability to "grab a card" and add to your Card Wall allows users to quickly add new cards and continue working with Mingle just like you would with a physical card wall.

We have also further improved card Quick Add by allowing you to add cards immediately from almost anywhere in the project.

Take a look at “What’s new in Mingle 3.5” for all the information on the latest features and enhancements.

How do I get Mingle 3.5?

Please download the latest installers take advantage of the new features. Details of the system requirements as well as detailed instructions on installing and upgrading to Mingle 3.5 can be found in our Mingle 3.5 help.

Share your thoughts...

Join our Template Exchange community to tell us what you think about the templates in 3.5 and share your templates with other Mingle users.

Please send us all your feedback as we look forward to hearing what you think of Mingle 3.5.

Happy Holidays
- The Mingle Team

Hello Studios Community

The Mingle team is happy to announce the newest release of Mingle, Mingle 3.3.1.

This release now supports Oracle 11g and includes additions to our formula property functionality, API updates and has further integration with Go, our Agile release management solution. The Mingle “What’s new in 3.3.1” help has complete details of the updates in Mingle 3.3.1. The Mingle Bug space has more information about the bugs fixed in Mingle 3.3.

To get your hands on Mingle 3.3.1 and take advantage of the new features please download the latest installers. Details of the system requirements as well as detailed instructions on installing and upgrading to Mingle 3.3.1 can be found in our Mingle 3.3.1 help. If you need assistance upgrading Mingle you can, as always, contact our support team for help and advice.

Please post your thoughts about Mingle 3.3.1 in the Mingle general discussion and in the Feature request space.

Thanks
- The Mingle Team

Hi all

We are happy to say that the release of Mingle 3.3 is just around the corner and before the GA release is made available in January 2011 we'd like to update you all on what the Mingle team have been working on over the last few months and what you should expect to see in Mingle 3.3.

First of all we are excited to introduce a new feature called User Groups. This feature allows Mingle and project admins to create and manage project user groups, use these groups to manage transition permissions within a project and share groups in project templates. We anticipate that this feature will further improve workflow creation whilst still allowing you to manage your team members in a way that makes sense for your teams.

In keeping with our theme to improve user management across the product we have also given Mingle and project admins the ability to add users to one or more projects at once and assign a user's project permissions when adding them to a project to allow for more efficient project membership management. The ability to see user last login information and the ability to filter out deactivated users has also been added aiding user management at the Mingle instance level.

Beyond the UI we have also added a powerful Event API which provides full, robust access to all events in a Mingle project to users and custom integrations, in the form of an Atom feed. All you budding Mingle integration developers, we look forward to your fun and useful integrations using this feature! Please share them on our Add-Ons and Extras space.

Finally Mingle 3.3 will be a more refined and mature looking Mingle as it heads into its fourth year. We hope you'll like our new style as much as we do.

That's all for now folks, but rest assured we will be providing more information on the release and all Mingle's new features and improvements when the GA is made available.

Thanks
- The Mingle Team

Thank you for trusting ThoughtWorks Studios to provide you with the products, services and enterprise-level of support for Mingle and MySQL technologies.  We take this responsibility very seriously!

From time-to-time, we must decide that the continued support and enhancement of a particular product is not in the best business interest of the Company.  When this occurs, we will begin an end of life (EOL) process for this product.  The goal of ThoughtWorks Studios' EOL process is to provide our valued customers with ample lead time concerning this decision so that each customer may transition from its use of the EOL product to an acceptable alternative.

For more information on the ThoughtWorks Studios Lifecycle Policy Click here

Mingle 3.0 - Support Ending for MySQL Database Server

Beginning with Mingle 3.0, using MySQL as your Mingle database will no longer be supported.  All existing MySQL users will need to migrate their data to either Postgres (Version 8.3) or Oracle 10g before upgrading to Mingle 3.0.

In order to facilitate a smooth upgrade to Mingle 3.0 for all MySQL users, we recommend that you upgrade to Mingle 2.3.1 and migrate your data to either Postgres or Oracle before the Mingle 3.0 release is available. Mingle 3.0 will be available in early December and we hope by then all MySQL users will be migrated to Postgres or Oracle so they can upgrade easily to Mingle 3.0.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Supported Databases

PostgreSQL

Mingle works with PostgreSQL 8.3

You can download PostgreSQL Version 8.3 from here

Note: Currently we are testing Mingle with PostgreSQL version 8.4 and support is expected to be extended by beginning of 2010.

Data Migration tool

You can download the Data migration tool from here 

The PostgreSQL Mingle database migration script is a tool to migrate a Mingle MySQL 2.3 or 2.3.1 database to Mingle PostgreSQL 2.3 or 2.3.1 database.

Please follow the instructions mentioned in the README file to migrate from MySQL to PostgreSQL.

Oracle

Mingle works with Oracle 10g

You can download Oracle10g from here 

Data Migration tool

The tool is a bulk export and import tool which was shipped with Mingle 2.3 and 2.3.1.  This tool can be found in <MINGLE_HOME>/tools directory where <MINGLE HOME> is the directory where Mingle 2.3 or Mingle 2.3.1 is installed.

To use this tool please follow the instructions in the <MINGLE_HOME>/tools/export_import/readme.txt.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

FAQs:

1. Why is MySQL no longer supported?

Mingle launched with MySQL, and therefore ThoughtWorks Studios has had a long history with it.  Over time, we have had a few critical issues associated with MySQL; issues that have required significant bandwidth from our team to resolve.  Based on the publicly available roadmap for MySQL, we determined that the fixes we desire will not be addressed in time to accommodate our product development schedule.  Therefore, we decided to move away from MySQL.  We realize this will be a difficult transition for some customers, but in the interest of product quality we feel that this is the wisest choice.

2. How do I choose between PostgreSQL and Oracle?

Broadly, we'd suggest PostgreSQL unless Oracle is already in use in your environment and you have a dedicated DBA

Here are some criteria to consider

PostgreSQL:

* Installation is quick and configuration is relatively easy

* Ongoing administration is relatively straightforward

* PostgreSQL is a free, open source database, distributed under a BSD-style license.

Oracle:

* Requires a degree of performance tuning for optimal Mingle performance

* Installation can be time consuming

* Higher system resource requirements than PostgreSQL

* Well supported by third-party enterprise monitoring and backup tools.

3.   How do I migrate from MySQL to PostgreSQL?

The MySQL to PostgreSQL migration tool is available here

4. How do I migrate from MySQL to Oracle?

The tool is a bulk export and import tool which was shipped with Mingle 2.3 and 2.3.1.  This tool can be found in <MINGLE_HOME>/tools directory where <MINGLE HOME> is the directory where Mingle 2.3 or Mingle 2.3.1 is installed.

To use this tool please follow the instructions in the <MINGLE_HOME>/tools/export_import/readme.txt.

5. From where can I download PostgreSQL?

Mingle supports PostgreSQL 8.3

You can download it from here

6. From where can I download Oracle?

Mingle supports Oracle 10g

You can download Oracle10g from here

7. Where can I find the instructions to install PostgreSQL?

PostgreSQL 8.3 documentation

8. Where can I find the instructions to install Oracle?

Oracle 10g documentation

Hi all

As well as a variety of new features, Mingle 3.2 includes the following bug fixes.

Bugs related to source repositories

• Failed to import project due to Hg password problem.[Hg plugin]
• If P4 client is not installed, provide error message when user go to "Source" tab.

Bugs related to LDAP

• Prevent user login on Mingle if user does not belongs to specific ldap group.

Bugs related to Mingle instance management

• Mingle admins do not receive e-mails for subscriptions (unless they are also a project member)
• "Manage Users" link causes 500 error on instance hosting more than 200 projects
• Improve time to create project from template when Mingle has many users and many auto-enroll enabled projects

Bugs related to MQL

• Using NUMBER = THIS CARD.'relationship property name' in a WHERE clause should work
• Making chart with MQL that uses DISTINCT and ORDER BY will cause SQL error.[Oracle] 

Others bugs

• Cross project card link will be broken if attachment's name in inline image ends with digit
• URLs with special hyphens (en dashes and em dashes) are not rendering correctly in our wiki pages
• Transitions on grid view are creating card version but not changing card when ranking is on
• Provide user friendly error message when user tries to update a property which is not available to the type via the API

Thanks

- The Mingle Team