Taffy 1.1 RC1 Available
I've been working hard, in my nooks and crannies of free time, to put together and release Taffy 1.1. Lots of stuff has changed for the better, and it's a pretty sweet upgrade, if I do say so myself.
Luckily, I haven't been working alone. To date, I've had community contributions in the form of code, help testing, and advice from (in no particular order other than that with which they came to mind) Brian Panulla, David Long, Greg Moser, Dan Lancelot, Steve Rittler, and Barney Boisvert. There are more, I'm sure; and I'm deeply sorry for forgetting them/you!
But recently I realized that work has stagnated a little bit. Releasing version 1.1 has been held up for more than 5 months now almost entirely by my desire to add support for Railo. While I'm all for the open source movement (Taffy is open source after all), and the people working on and for Railo are some pretty nice guys, I just can't let that continue. So I'm going to release 1.1 soon, with or without Railo support.
Don't get me wrong, I'd still love to have it supported and I'm happy to review any pull requests anyone sends in. It's just that I've had a hell of a time getting a decent environment setup to run my tests and work out the kinks, and while there has been some support from the Railo community, I'm afraid to say it's just not been enough.
So to that end, I'm posting Taffy 1.1 Release Candidate 1 (RC1) here today. You can download the zip and play with it, but the best thing you could do would be to clone from the 1.1-rc branch on github to make it easy to get the latest updates. So what's left to do before this release candidate is declared final? Most importantly, I need to finish the documentation updates. I've got a lot done that was published earlier today, and there's still some more to do. And of course, I need people to play with it and report any bugs you find!
And, if you're in a giving mood, I'll be keeping the Railo branch up to date. This branch is designated for testing and sharing Railo-specific fixes, and then once they are confirmed working in Railo and confirmed not to break against Adobe CF, I'll merge them into whatever the current dev/RC branch is.
I really hope that the Railo community can help me finish what's left to get their platform supported, but in the end it boils down to shipping 1.1 being more important --for me, at least-- than including Railo support.
Look for a post soon outlining some of what's changed since 1.0. I'm pretty excited about it! You can get a preview of that post here on the roadmap, if you just can't wait.
- Taffy version:
- 1.1 rc1
- Project:
- https://github.com/atuttle/Taffy
- Download:
- Zip from Github
in Taffy Posted 2011-10-27 12:30
6 responses:
I don't know how many times more I can tell you to open up tickets or join the mailing list to discuss the issues. Bugs don't get fixed unless you report them. Conversations don't happen unless you start them.
Still waiting for you to file a ticket and start a discussion, because I've yet to see it happen.
Sorry we 'supposedly' couldn't support you.
I have participated a little bit on the mailing list. My issue mostly revolves around my difficulty getting anything other than the Railo Express edition to work (JEE continually perplexes me), and the fact that the Express edition uses Jetty, which doesn't support Wildcard servlet mappings.
Once I can get a usable testing environment, I can start to work through the incompatibilities that may exist in Taffy. Honestly, I would love it if someone else would do that for me -- the unit tests are there and all run perfectly on ACF -- but I don't expect anyone to. That's the curse of the open source developer.
But at the same time, I don't use Railo regularly. In fact, my only regular exposure is supporting it in my open source projects. I don't have a lot of intrinsic motivation to support Railo, and I've only had one or two requests from people who wanted to use it with Railo, so I don't have a lot of extrinsic motivation either. So really, my only motivation is to try and be supportive of your platform and community by making Taffy work well with it. There's only so far I can go (working at it off and on for 5 months, apparently) before I decide that it's just not worth the trouble and proceed without it.
Like I said in the post, I welcome anyone to try and help fix the incompatibilities. I try to be very good about reviewing pull requests on Github, for all of my projects, and I welcome any and all community contributions as long as they contribute to the product in a constructive way.
I hope you don't take my post as an attack on Railo. It's anything but that.
Since then, it has been decided that ACF is moving to Tomcat. I'm sure Adobe will be porting their black magic voodoo connector to make it all happen behind the scene, but... Tomcat is coming to a ColdFusion server near you and you wouldn't hurt to be prepared for future issues.
I think you need to come back to the mailing list, square one and tell us what JEE issues you're having so we can work that out. This is the first I'm hearing you complain about it.
Here's a post on the Taffy mailing list explaining what you'd need to do: https://groups.google.com/d/msg/taffy-users/Dajw-d30ZQY/6ml-RubGFVAJ
Leave a comment: