Tracker Cleanup

I have created a canned response called 'wxRuby 0.6.0
Cleanup' and will 
now go and mark as closed all open 0.6.0 messages.  If you
strongly 
disagree with this, they can always be re-opened.  The text
of the 
message is:

Requests for support for wxRuby 0.6.0 have been closed so
that we
may focus on wxRuby2.  No further work will be performed on
wxRuby 0.6.0.  Please download and try wxRuby2 to see if
your
problem has been resolved.  If not, please submit a new
report
describing your problem with wxRuby2.

Roy
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

Sounds good. There shouldn't be that many left - most have 
either been 
closed or updated if they are still relevant to wxruby2.
Probably best 
to focus on build errors that sound out of date.

alex

Roy Sutton wrote:
> I have created a canned response called 'wxRuby 0.6.0
Cleanup' and will 
> now go and mark as closed all open 0.6.0 messages.  If
you strongly 
> disagree with this, they can always be re-opened.  The
text of the 
> message is:
>
> Requests for support for wxRuby 0.6.0 have been closed
so that we
> may focus on wxRuby2.  No further work will be
performed on
> wxRuby 0.6.0.  Please download and try wxRuby2 to see
if your
> problem has been resolved.  If not, please submit a new
report
> describing your problem with wxRuby2.
>
> Roy
> _______________________________________________
> wxruby-users mailing list
> wxruby-usersrubyforge.org
> ht
tp://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>   

_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users