Mylyn 2.2 released, new webinar available
, December 21st, 2007Mylyn 2.2 has been released. Check out the New & Noteworthy for the full listing of enhancements that correspond to the 384 bugs resolved for this release. A whopping 67 bugs were resolved by community contributions, and those include useful enhancements such as the improved screenshot facility. Credits are in the New & Noteworthy.
This release comes along with a new webinar, courtesy of Eclipse Live, to help you get the most out of Mylyn 2.2. Happy Holidays!
December 21st, 2007 at 4:31 pm
Good stuff Mik, keep up the good work.
December 22nd, 2007 at 7:43 am
News and Noteworthy should mention in addition to the cached configuration mentioned (using If-Modified headers) that GZIP content encoding is now also supported for the bugzilla connector, not just for the configuration but all interaction. Instructions on how to set up a cached config and gzip yourself are on:
http://wiki.eclipse.org/Cached_Repository_Configuration
For full bandwidth savings use mod_gzip (Apache 1.3) or mod_compress (Apache 2)
December 24th, 2007 at 12:06 pm
[...] have hooked Mylyn up to our Trac. Here’s a webinar on version 2.2 and an interesting article from the New Yorker on checklists. 0 Comments Posted by [...]
January 9th, 2008 at 4:54 pm
Maarten: we tend to leave out implementation and performance improvement details of that sort from the New & Noteworthy documents in order to avoid them getting too long. In this way some of the most notable improvements to Mylyn are things that users will not notice because they help keep the tool out of their way as they get things done. This one was definitely a useful contribution from you and I bet that a lot of people now simply think that bugs.eclipse.org is running faster
On a related note, for Mylyn 2.2 we got rid of forcing the user to specify whether the repository has a cached configuration enabled, so this implementation detail is now completely hidden. Server administrators do need to know about it though, so I moved your instructions to the User Guide. At a later point we could consider creating an administrator guide.