YUI 3.6.0 PR4 Now Available
By Allen RabinovichJuly 18th, 2012
YUI 3.6.0 PR4 is now available to the developer community for feedback and testing on the Yahoo! CDN. Please take a minute to check it out via CDN or download.
The target date for the stable release of 3.6.0 is July 31, 2012.
You can check out the list of issues addressed in 3.6.0 PR4 in our bug tracker. Additionally, you can take a look at the current change history rollup for all components in the library.
PR4 also contains a couple of new modules: the ModelSync.REST extension, transitioning from its previous home in the Gallery, and the LazyModelList class.
We invite you to join the ongoing development discussions happening with the team over on GitHub. For support, visit our forums, or join other YUI developers live in the #yui channel on irc.freenode.net (a web client is here).
Thank you again for all your feedback and happy testing!
July 18, 2012 at 5:18 pm
> Changed the default throwFail behavior to act like it sounds, see ticket #2531679 If throwFail is true (default) we will not wrap modules or the use callback in a try catch. If it’s false, they will be wrapped (the old behavior).
Thanks so much for that one! Chrome was taking ages to fix the rethrow issue.
July 19, 2012 at 6:26 am
Given the number of open 3.6.0 issues, many of them important, and the small number of issues in pr4, many of them test related, and the target date for release, it makes me go hmmmmm
July 19, 2012 at 10:23 am
Marc,
I assume you’re talking about this list:
http://yuilibrary.com/projects/yui3/report/126
You’ll notice that most of the 3.6.0 tickets which are still open are ones which are either not assigned to a sprint or assigned to the backlog.
Things that we’d like to get to, but fall outside a releases sprints, we assign to the backlog with the hopes that we can get some of those in the reason.
July 19, 2012 at 2:21 pm
@Marc,
How right you are that PR4 addresses a fewer number of issues than normal! We’ve been in the process of condensing our development cycle in order to transition to monthly releases. As part of that ongoing work, the team spent time this past sprint to automate our library-wide functional test suite. That important work will now help us to move much faster, so thanks for your patience and understanding!
July 21, 2012 at 5:09 pm
Thx for the update. As far as I can see it, YUI2.9 was only released last year (April 2011) and it’s still very robust. Also, not all widgets have been ported. Paginator, treeview was builtin. Once the API for 3.x is stable I’ll migrate but I’ll stick with 2.9.0 for now since it’s very stable.
July 27, 2012 at 2:22 pm
Also,
>
http://yuilibrary.com/forum/viewtopic.php?f=18&t=9737&view=next
>>
Our project has been struggling with this for a while. Our app is fairly large and uses many YUI2 components. The problem we have is that most of the equivalent YUI3 components are still marked beta. We are not permitted to use beta components in a production application and we don’t have the resources available to even begin a prototype port. Unfortunately, we are still building new functions of the app and have no choice but to continue using YUI2. Once the app is complete and if YUI3 survives then we will plan a migration. I’m starting to think at that point dojo will be a better option. It has equivalents for nearly all the YUI2 components we use (DataGrid, Dialog, Menu, ProgressBar, json, io, etc). I’m not saying that dojo is better than YUI, but given YAHOO’s current situation dojo seems like a better option as it has the support of several large (stable) companies like IBM.
>>
+0-
For myself, it has been a bit of a struggle to upgrade from yui2 to yui3. I do like the way YUI3 works in general and think it will be great given more time. However, I find the lack of available widgets to be a large roadblock.
For example, tried to get tooltip working today and there is only an example provided somewhere which doesn’t seem to work appropriately in my case ( kind of works but kind of screws some other stuff up). Spent way too much time trying to get menu to behave like a split button in yui2.
YUI3′s use case currently seems to be: come to YUI3 and build all the widgets you want on top of our cool infrastructure! uhhh… don’t really have time for that