Call to arms, implementing and preparing the 1.0 release

[Philip Van Hoof <spam pvanhoof be>]

Coders and people with know-how can help me with preparing the release


ABI and API guards

	- Currently there's a $(API_VERSION) in the build scripts and
	  the configure.ac extracts the ABI version number and prints
	  it. Is this enough? Can we improve things?

	- Functions that start with an underscore are not exported. Is
	  this a good idea? I have this from the libgtk build
	  environment

	- Searching for locations where ABI might get into troubles.
	  Reordering methods and properties in such a way that the most
	  unlikely-to-change are at the top of the structs.


Packaging

	- Packages for camel-lite-builder
		- That don't conflict with o-hand's eds-dbus packages
		- For Maemo, OLPC and GPE
		- Desktop packages for Ubuntu, SuSe, Fedora, etc that
		  don't conflict with evolution-data-server

	- Packages for tinymail
		- For Maemo, OLPC and GPE
		- Desktop packages for Ubuntu, SuSe, Fedora, etc

Final design

	- There's still two more design refactors that I would like to
	  do before releasing:

		- Letting an account return its folders how a folder
		  returns its headers (by byref passing a TnyListIface
		  in stead of letting the method return it)

		- Split up the store-account types into nntp, imap and
		  pop in stead of having the current ugly switch/case
		  crap

Implementations before release 1.0

	- Currently there's no working POP implementation. The only
	  thing this implementation should (for now) do is to fetch
	  messages from the POP service and store them in a mbox. And
	  let the store-account of tinymail use that mbox in a
	  CamelFolder instance.

	  How it fetches it, I don't care (fetchmail, whatevermail or 
	  by using the support in Camel)

	- A GtkHTML TnyMsgViewIface implementation. Modest is going to
	  have one: I would like to get this one in the tinymail
	  repository. Whether or not this will be usable depends on
	  licensing and an approval of Nokia (Dirk-Jan, do you have more
	  on this?)

Implementations before or post release 1.0

	- Support for summaries in the pop provider of Camel


Integration before or post release 1.0

	- Integration with Seahorse for PGP checking



-- 
Philip Van Hoof, software developer at x-tend 
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
work: vanhoof at x-tend dot be 
http://www.pvanhoof.be - http://www.x-tend.be