On Wed, 2008-07-16 at 02:32 +0200, Jonny Lamb wrote: > Hi all, > > SynCE 0.12 is out. There would be comic names for SynCE releases, but > we're just too solemn for that kind of thing. >
<grin> > What's new > ========== > > There has been steady progress with this release. I will not summarize > here -- check out the SVN logs. The roadmap for this release and its > status can be found at: > > http://synce.org/moin/SynceRoadmap > I have kernel questions, but that's another thread. > As you can see, most things were implemented. Other than that, you'll > have to dig deeper yourself, sorry! > > If you have any big cool ideas about the future of SynCE, its direction, > and any feature you'd love to have around, let us know. We will not > promise anything, but are interested to hear your thoughts! > > New files and their md5sums > =========================== > > 80aa988bb37e40066abf204c6a8d6f7a librapi2-0.12.tar.gz > 867b29f88df6a7706c2a4b2bda658c9e librra-0.12.tar.gz > fd473d3deceda7912af4427dede1736f libsynce-0.12.tar.gz > 03c833e4adb5ec17d32ac338cf1a6d18 odccm-0.12.tar.gz > b460273d980c6ce0289f0beca9484f78 synce-gnomevfs-0.12.tar.gz > 06c7fe3d2b9c130cd485272d6756f599 synce-hal-0.2.tar.gz > 8ea4995167ae8a5014eb9504bde51281 synce-kpm-0.12.tar.gz > 2886545a8f7a029063b9b5f804806e23 sync-engine-0.12.tar.gz > > You can find these files on your favourite SourceForge mirror. These > will also turn up in distribution repositories some time soon. I'll try > and get them into Debian soon, but I severely doubt they'll make Lenny. > > Missing files > ============= > > I did not release synce-trayicon or gvfs because their Makefiles are broken > and I couldn't create a dist tarball. Once this is fixed, I'll be more > than happy to release! > What happened with trayicon ? I keep forgetting to test make dist... gvfs I don't know what to do with yet. > I did not release kde-rapip{,-kde4} because I was unsure whether it was > wanted. I had a quick look through synce-devel archives and noticed that > when I asked this question, I got no answer. If you want it released, > tell me. > I'd say yes, but packagers will have to bear in mind to make it conflict with synce-kde. > Development notices > =================== > > For all new releases I will *not* be bumping the requirements on any > libraries inside configure.ac files. I could be wrong, but I feel that > they aren't being updated properly, so I'm upping the deps on every > release, which is probably rather unnecessary. If you implement > something in a module which requires the development version of, say, > libsynce, depend on the current version + 1. > > Although, this now does depend on setting the library versions > "correctly". The way it should be done AFAIK, as I pointed out to Guido > today, is that once a, say, 0.1 release is done and tarballs are > released, the version number in configure.ac should be increased. This > helps with the previous case of deps, and it also makes it clear if > someone is running an development version. > > I will try and get this done soon, but I'm very busy at the moment. > Agreed. I've often made commits that depend on something else since the last release, with no way to make that clear. Maybe we should only bump the version in svn after something has been committed, otherwise we imply changes that haven't happened. Too complicated ? Mark
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
