Anjuta Roadmap

2.30

Add/Remove/Rename of files in file-manager and/or project-manager should update the status of VCS

Provide "Locals" support for files not conained in the project on-the-fly (maybe in-memory database).

Allow more drag and drop operation in the project manager view, Read include file in automake files, Display libraries like targets... Seb is working on it but it will not be ready for this release. Then, we can go even further like supporting additional kind of project CMake by example or allow updating makefile.
Faster startup time. Anjuta is a bit slow to be used just for editing one file. It will be useful to see if this can be improve. A though performance needs to be profiled and studied where the bottlenecks are.
Global rename, code refactoring. From time to time, we change the name of one type or one variable, it would be really useful if we can easily do this. Currently, we can use the search plugin, but if the variable has short name, it will probably give too much false positives. We can probably do much better parsing the source code, perhaps using information from symbol-db.

To provide means to extent Anjuta in varying ways.

Encouraging bindings for other languages. This is essentially a gateway to many interesting plugin developments involving language specific plugins. I believe our framework is at very good position to support language bindings, thanks to Sebastien. But we need more efforts to promote this and give guidance (documentation, website, demonstration, examples) to prospective 3rd party developments.
Provide remote templates download for user to just browse and find his right template. Also to allow uploading new templates. This will need some kind of web service, but I think it can be worked out somewhere in anjuta.org. However, the biggest issue is maintaining it in user's installation. Maybe it's just better to depend on host packaging system to avoid reinventing the wheel?

Since we are now part of GNOME suit, reliability is becoming more important. We need to focus on automated testing also. While clearly we don't have the resource to go full blown test suit, we can hopefully have some regression testing for complicated features that have way too many test cases typically not easily covered in normal usage.
Module testing is also interesting. We could come up with some generic module testing setup that would allow independent plugin testing without involving other plugins too much. We have some basic setup using anjuta-shell, but something better can be thought out.