On Wed, 2007-12-05 at 15:32 +0000, Jonny Lamb wrote:
> Hi everyone.
>
> A fairly long email with some various thoughts on several things. This
> is meant to spark up discussion, so please do reply!
>
> 0.11
> ====
>
> I think this needs to be released pretty soon. However, there are some
> things that need to be sorted first:
>
> * Documentation -- yes this is the obvious one. Nothing really to say
> about this.
> * Various fixes -- known bugs in the software that don't require a
> whole new rewrite should really be fixed before the release. Please
> can you all reply with problems that spring to mind when I speak
> about this, so I can keep track of the progress.
>
> Rather a general "what needs to be done" list. Please do reply with
> specifics! I suppose I'm suggesting we put in a freeze now and
> concentrate on bugs, for the release.
>
> 0.10.0 to 0.11 (There's no point in an extra ".0" in "0.11" as there's
> not going to be a "0.11.1" -- "0.10.0" was perhaps a little optimistic!)
> isn't going to be the biggest update ever, but there are several nice
> new features or fixes. Things that come to my mind now:
>
> * Samsung SC* phones fixed with usb-rndis-lite.
> * odccm now supports legacy devices.
> * WM6 support.
> * Various other fixes in SyncEngine.
>
> Again, please fill the gaps here.
>
> I think a new release will be very good for the project. It will provide
> milestones that will be acceptable and doable for developers. It will
> show SynCE as still being active and the new docs will make the project
> more usable. The docs are currently what is stopping me pursuing
> actually getting packages into Debian (and then perhaps Ubuntu), so that
> would be started again.
>
> Further goals
> =============
>
> After 0.11 there will be some other features and fixes that will be
> worth investing time in. Two I can think of now are:
>
> * Simplifying the installation process, significantly.
> * Removing the libwbxml dependency.
>
> If you have any other ideas, please state them here. If the idea has not
> previously been aired, please give some information about it.
>
> Other talking points
> ====================
>
> vdccm: It seems to me that the only advantage of vdccm is its multiple
> device support. Therefore, I am suggesting dropping vdccm as a proper
> SynCE module. I'm not saying it should be deleted from SVN, but just
> left out of releases. Thoughts?
>
> ML moderator: I am currently looking for someone who will help out by
> moderating the mailing lists. This basically takes two minutes every few
> days or so and involves just filtering out spam from real mail. This
> effort keeps the SynCE mailing lists spam-free. Email me if you are
> interested in helping out, or would like to know more.
>
> UK meetup: There are a few of us in the UK (myself, John Carr, J. A.
> Gow, Mark Ellis, more?) -- John Carr and myself have spoken about
> meeting up but I've been tremendously busy this term starting uni and
> all that. Would anybody be interested in this?
>
> I hope this is easy to read and is not too boring! :-)
>
> Kind regards,
>
Hi,
I am working very heavily on sync-engine (literally every spare moment
at present) to considerably clean up the partnership code and fix a lot
of latent issues with it (and there are quite a few which may not have
shown up in general use yet), also to fix a couple of WM6 bugs and add
important features (already have DTPT working from within sync-engine
obviating the need for a seperate module). These are substantial
changes, improvements and fixes so it may be worth holding off on a
release until I can commit these in the next week or so.
Note I am testing these changes on a daily basis in my production
environment (either confident or stupid, I haven't worked out which
yet :-) and I don't really want to commit them until I can be sure they
work and aren't going to trash anything, so I am looking at a timescale
of about a week before they should be ready.
I'm trying to use as much available time as possible for actual coding
at the moment. I'll keep an eye on the bug tracker when possible but it
may speed things up if someone could be kind enough to batch up all the
current known sync-engine bugs or odd behaviour especially if not in the
tracker, and send it to me in one mail. I will try then to get fixes in
with the new code.
Regarding a UK meet: this sounds like an excellent idea!
John.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
