Update: As of today, I've pulled rails3 into master, so that's not the main active branch. Also released a new version (2.0.0) to Rubygems.
As for your question; it's hard to say. The jquery branch is pretty stable, except for those few bugfixes you mentioned. The problem with merging it in is that any existing apps (like, say, Curbly.com) will have a pretty rough upgrade path since the jquery branch changes so much of the underlying html. In particular, apps with modifications or overrides to the view templates will have a tricky upgrade in store for them. I'd love to hear suggestions for how to eases this pain for people. My tendency right now is to just leage jquery-bootstrap where it is (if someone wants to pull in bugfixes from master, that'd be cool), and let people choose it as a starting point for new apps, or upgrade existing apps over time. Thoughts? Bruno On Fri, Dec 7, 2012 at 11:51 AM, Kevin Lawrence <[email protected]>wrote: > Of course, I should have asked: 'anything I can do to help?' :-) > > > > On Friday, November 30, 2012 1:57:51 PM UTC-8, Kevin Lawrence wrote: >> >> Any idea when that merge might happen? I've run across a couple of little >> bugs that are fixed on the rails3 branch but not the jquery-bootstrap >> branch. >> >> >>> -- > You received this message because you are subscribed to the Google Groups > "CommunityEngine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/communityengine/-/RoG2SKAjy9EJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/communityengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/communityengine?hl=en.
