You might want to know why RC3 hasn’t appeared yet.
We’ve squashed the custom field search bug. (Thanks, Ruslan!)
We’ve reverted the task linking behavior. (The change in RC2 based on
mailing-list agitation actually breaks compatibility with 3.4.)
But we’re still seeing some test failures on Postgres that we’re looking
into.
Once that’s sorted, we’ll be sure to get RC3 out to you as quickly as
possible.
JEsse
You might want to know why RC3 hasn’t appeared yet.
We’ve squashed the custom field search bug. (Thanks, Ruslan!)
This bug is not fixed, at least as of revision 5289 (current as of this
morning). It is fixed if the DB is MySQL (and possibly others) but it
still exists if the DB is SQLite (and presumably Oracle based on
Rangarajan’s issue). I’ve been trying to look into why it is still a
problem when using SQLite, but I haven’t had much time to devote to it.
Thanks.
Joshua Colson jcolson@voidgate.org
You might want to know why RC3 hasn’t appeared yet.
We’ve squashed the custom field search bug. (Thanks, Ruslan!)
This bug is not fixed, at least as of revision 5289 (current as of this
morning). It is fixed if the DB is MySQL (and possibly others) but it
still exists if the DB is SQLite (and presumably Oracle based on
Rangarajan’s issue). I’ve been trying to look into why it is still a
problem when using SQLite, but I haven’t had much time to devote to it.
SQLite is great for testing, but I wouldn’t trust it for any sort of
production deployment. An actual failing test would be useful.