== Ruby Reports (ruport) 1.0 ==
It’s been a long and wild ride. We’re proud to announce that we’re at
the end of our long list of feature requests and planned changes on
the 1.0 roadmap, and that with your help, we’ve beaten up the RCs
enough to shake out a lot of the major bugs, as well as fix some
surprising behaviors and minor annoyances. So, by some luck of the
gods, we’ve managed to keep our scheduled release date and Ruport 1.0
is now ready.
== We now have real web content! ==
We’ve fleshed out rubyreports.org with enough info to get you started.
The front page explains a bit more about the project and points you
at all of our available community resources such as mailing lists,
wiki, etc.
If you’re interested in some more release details, there are some
extended notes up there:
http://rubyreports.org/release_notes-1.0.html
== Get it ==
gem install ruport -y
== That’s all ==
I had contemplated massively long release notes, but I figure 1.0 is
only especially exciting for those who already are following the
project. 
Please do stop by our mailing list and say hello
(http://list.rubyreports.org)
-greg
PS: For some nostalgia, check out my first post about Ruport
(from August 2005)
http://groups.google.com/group/comp.lang.ruby/msg/69fc1c10f41d90c5
On 5/14/07, Gregory B. [email protected] wrote:
It’s been a long and wild ride. We’re proud to announce that we’re at
the end of our long list of feature requests and planned changes on
the 1.0 roadmap, and that with your help, we’ve beaten up the RCs
enough to shake out a lot of the major bugs, as well as fix some
surprising behaviors and minor annoyances. So, by some luck of the
gods, we’ve managed to keep our scheduled release date and Ruport 1.0
is now ready.
Congratulations.
Are you going to be at RailsConf this weekend? Myself and probably
some other folks from ThoughtWorks would like to meet you.
Best regards,
Alex Verkhovsky
RubyWorks team
ThoughtWorks
On 5/14/07, Gregory B. [email protected] wrote:
== Ruby Reports (ruport) 1.0 ==
It’s been a long and wild ride. We’re proud to announce that we’re at
the end of our long list of feature requests and planned changes on
the 1.0 roadmap, and that with your help, we’ve beaten up the RCs
enough to shake out a lot of the major bugs, as well as fix some
surprising behaviors and minor annoyances. So, by some luck of the
gods, we’ve managed to keep our scheduled release date and Ruport 1.0
is now ready.
My congrats to you and the others involved on your team!!
I know all too well the challenges involved in keeping open projects on
track, so this is an awesome accomplishment!
I’ll plan to mention about Ruport 1.0 at our next St. Louis Ruby U.
Group
meeting next week and I expect that we’ll need to follow up with a
formal
presentation beyond that (since I know they’ll want to hear more).
Job well done!
Gregory B. wrote:
== Ruby Reports (ruport) 1.0 ==
It’s been a long and wild ride. We’re proud to announce that we’re at
the end of our long list of feature requests and planned changes on
the 1.0 roadmap, and that with your help, we’ve beaten up the RCs
enough to shake out a lot of the major bugs, as well as fix some
surprising behaviors and minor annoyances. So, by some luck of the
gods, we’ve managed to keep our scheduled release date and Ruport 1.0
is now ready.
Sweet.
Congratulations!
–
James B.
“Tear it up and start again.”
On 5/14/07, Alexey V. [email protected] wrote:
Congratulations.
Oops, sorry for spamming the list.
Alex
On 5/15/07, Jeff B. [email protected] wrote:
My congrats to you and the others involved on your team!!
Thanks!
I know all too well the challenges involved in keeping open projects on
track, so this is an awesome accomplishment!
We’ve got more to do before we can hang up our hats, but I’m happy to
see Ruport fairly stable and useful now…
I’ll plan to mention about Ruport 1.0 at our next St. Louis Ruby U. Group
meeting next week and I expect that we’ll need to follow up with a formal
presentation beyond that (since I know they’ll want to hear more).
That sounds great. If you or your group have any questions just let me
know.