C
Curt Hibbs
Its been a little over three weeks since I released the first preview
of Instant Rails. In that time there have been over 3,000 downloads,
but very little little feedback.
This tells me either that it is not being used (which would be bad) or
that it is being used but no one is having any significant problems
(which would be very good). So, if you are using it, but are just not
having any problems, I'd like to here from you just to get that
feedback.
The final 1.0 release for Instant Rails will be sometime after the
first of the year because I want it to include the released version of
Ruby 1.8.4 and the final release of Rails 1.0.
My plans also include upgrading to Apache 2 (currently it contains
Apache 1.3.33) as well as a more recent release of MySQL. Please help
me with a couple of decisions/priorities here:
1) Is moving to Apache 2 important to you, or or you happy with Apache
1.3.33 for the time being?
2) Should MySQL be upgraded to the latest 4.x release (currently
4.1.15) or would you prefer it be upgraded to 5.0.x?
Thanks,
Curt
of Instant Rails. In that time there have been over 3,000 downloads,
but very little little feedback.
This tells me either that it is not being used (which would be bad) or
that it is being used but no one is having any significant problems
(which would be very good). So, if you are using it, but are just not
having any problems, I'd like to here from you just to get that
feedback.
The final 1.0 release for Instant Rails will be sometime after the
first of the year because I want it to include the released version of
Ruby 1.8.4 and the final release of Rails 1.0.
My plans also include upgrading to Apache 2 (currently it contains
Apache 1.3.33) as well as a more recent release of MySQL. Please help
me with a couple of decisions/priorities here:
1) Is moving to Apache 2 important to you, or or you happy with Apache
1.3.33 for the time being?
2) Should MySQL be upgraded to the latest 4.x release (currently
4.1.15) or would you prefer it be upgraded to 5.0.x?
Thanks,
Curt