Hello all -
To cut to the chase: I've had it with SourceForge. Their latest site redesign has made the entire site extremely painful to use and administer.
So, we will be moving development to BitBucket. The SF site will indicate that we've moved and will continue to house older releases and the old CVS and SVN repos.
Git will be used for version control on the new repo.
Over the next week or two I'll be transitioning things over. I'm planning this order for the process:
We're overdue for a maintenance release, so I'll working on getting that out after the move is complete.
I'll keep this thread updated with progress. If you have any concerns or questions, ask away.
 Question number one, I'm sure, will be why we didn't choose GitHub. The answer is that they dropped support for file hosting (i.e., distributing release binaries) which I consider essential. Here is their announcement about it. Yes, I could set up Amazon S3 or Dropbox or something, but I use these sites to make it all easy. More work means we're less likely to bother fixing someone's bug (as illustrated by how long it's been since a Trove maintenance release happened).
Steps 1-3 are now complete. Please redirect your browsers to: https://bitbucket.org/robeden/trove
I've also created a Twitter account that will be used for commit announcements and release notices: https://twitter.com/trove4j
Tracker issues have all been moved. At this point the transition is pretty much complete.
I'm still considering what to do with discussion forums. For the moment, these will stay with SF.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.