Subscribe
The problem with this approach was that there were some MTOS cases that shouldn't have been public (because, for example, they might have a user's email address or other sensitive information, or relate to security vulnerabilities that had not yet been publicly disclosed) There are also many cases that are MT Internal that non-Six Apart employees should be able to see, like bugs and patches that impact enterprise consultants and developers.
Going forward, instead of MT Internal and MTOS, the MT fbz instance will instead have two projects, one public and one private, both of which can contain bugs in both the open source and proprietary portions of the product. To reflect this change, the MTOS project name has been changed to "Movable Type-External."
This shouldn't change too much for the MT community, but it means that if you wish to enter a bug report for the Pro or Enterprise components of the product, you can do that directly instead of filing a case in the MTOS project, then having the case seemingly disappear when it was moved to MT Internal.
If you have any questions or concerns about these changes, or anything else relating to MT case management process, please let us know in the comments to this post.
Connecting mixi Users with Movable Type Communities
Connecting mixi Users with Movable Type Communities