I somewhat agree with Robin, that for the bug fixes and refactoring under the hood 2.7.0 is ok (it is already a big leap from the 2.6.3 version number). If the name it 3.0 it can be a disappointment for users if they won’t find anything “new” after they upgrade. Also if we use 3.0 now and then update the look and add some significant new features, then what number should we give it? 4.0? I don’t like fast major version number changes, though it is popular now (Firefox, Chrome). It is easy to get lost in those numbers, yet minor version number changes are easier to associate with fixes.
New skins and update to JTatoo, if it really looks different is a fine point for 3.0.0, but not enough, imho. Let’s take a look at this feature requests list and pick what would justify next major version bump http://issues.igniterealtime.org/secure/IssueNavigator.jspa?reset=true&jqlQuery= project+%3D+SPARK+AND+resolution+%3D+Unresolved+AND+issuetype+%3D+%22New+Feature %22+ORDER+BY+priority+DESC&mode=hide
Of course, someone would have to make those features and this is not an easy task Personally i would like to have separatable chat windows (a patch was in the works, but was never finished). Not for myself as i like one window approach of Spark, but for my users, who are using another client. SPARK-893 (additionally SPARK-935)
Other interesting features:
SPARK-916 Quarentine incoming messages when in DND mode
SPARK-634 Make drag and drop file transfer work in Linux
SPARK-996 Groupless mode
SPARK-1001 Add custom responses depending on the presence status
SPARK-1071 Add an option to automatically join ad-hoc group chat on invite
SPARK-1238 Add support for XEP-0184: Message Delivery Receipts
SPARK-1430 Create an installer for OpenSolaris/OpenIndiana
SPARK-1150 Allow the font face, size, colour & attributes (bold, italic, underline, strikethrough) to be changed
SPARK-1468 Make Spark compatible with WE4Java
Of course, most of these requests filed by me Or we can think of something new.