 |
Forums |
Admin Start New Thread
By: Matthias Tarasiewicz
RE: Failing Tests in Trunk [ reply ] 2007-09-27 06:57
|
hello phil, if you are still interested in helping out, please drop me a mail so i can add you to the svn -- in this case you could commit your patches to the instiki subversion repository.
let me know,
regards,
matthias
|
By: Shane Celis
RE: Failing Tests in Trunk [ reply ] 2007-08-22 01:29
|
Hello Phil,
The failing tests have been a bother to me too. However, I'm not even where to start to fix them. Here's the error that I'm getting:
$ rake test
(in /Users/shane/Projects/ruby/darcs-instiki)
wrong number of arguments (3 for 2)
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:725:in `fu_check_options'
[...]
Is that the same one you're getting?
|
By: Matthias Tarasiewicz
RE: Failing Tests in Trunk [ reply ] 2007-03-01 10:41
|
hello phil.
the 0.11 branch was just bugfixed with version 0.11.pl1 - this is definitely the last 0.11 version to come out. if there is some other serious rails-flaw, it might be that we have to release another bugfix version fast ;)
but since we are about to finish version 0.12, don't worry to much about version numbers....
|
By: Phil Thompson
RE: Failing Tests in Trunk [ reply ] 2007-02-28 10:53
|
|
Just to add I tested this on Linux (CentOS). I'm currently checking it out on Windows too so we'll see. I also notice that the 0.11 branch is still active so that's cool but it seems features are still being added here too. I find this a little strange but I've not worked on an open source project before so forgive me.
|
By: Phil Thompson
Failing Tests in Trunk [ reply ] 2007-02-28 10:27
|
Hi there, I've been looking at the current SVN trunk of Instiki and it seems a lot of tests are failing. I was hoping to do some bug fixing as I'm keen to bring instiki to a stable release as I like whats there but a few things need sorting.
Fixing test failures and deprecation warnings would be a good start but I'd like to know if anyone else is working on this at the moment.
Also wouldn't it be better to get it to a 1.0 release before adding any more features. I think it is usable in its current state so I think locking down the features until post 1.0 maybe a good thing. What do people think.
|
|
 |