Re: [Ekiga-devel-list] New branch for Ekiga 3.00

["Peter Robinson" <pbrobinson gmail com>]

>> > >>>>> OPAL and PTLIB have been branched for the Ekiga 3.00 release.
>> > >>>>>
>> > >>>>> Please use the new branches and not SVN TRUNK anymore.
>> > >>>> Is it possible to do the same for ekiga too?
>> > >>>>
>> > >>>> I have a few patches for after 3.0 already.
>> > >>>>
>> > >>>> And a few ideas too.
>> > >>> I would prefer waiting 1 week.
>> > >>> We also need to discuss how we will work for 3.2. I do not want the same
>> > >>> phenomenon than with 3.00 : 3 years of development without release.
>> > >> There are a few directions we can work on ; I shall name them and show
>> > >> (some) bugs assigned to myself which I consider of the category as example :
>> > >>
>> > >> (*) fixing bugs in current code
>> > >>
>> > >> (it's hopefully pretty empty just before the release, but we can expect
>> > >> it to grow just after...)
>> > >>
>> > >>
>> > >> (*) enhancements of existing code
>> > >>
>> > >>
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=548276
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=530617
>> > >>
>> > >>
>> > >> (*) cleaning of existing code :
>> > >>
>> > >>
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=552547
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=504937
>> > >>
>> > >>
>> > >> (*) better engine :
>> > >>
>> > >>
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=550278
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=550277
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=504936
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=552549
>> > >>
>> > >>
>> > >> (*) gstreamer :
>> > >>
>> > >>
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=339896
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=339897
>> > >> http://bugzilla.gnome.org/show_bug.cgi?id=399289
>> > >>
>> > >>
>> > >> Does it look good?
>> > >>
>> > >
>> > > Not at all.
>> > >
>> > > The reason is that there are no user visible or centric features. Let's
>> > > not make the same mistake than for 3.00.
>> >
>> > Having default categories is visible, and that is precisely why it can't
>> > be done for 3.0 : it would break string freeze!
>> >
>> > Having gstreamer devices would bring in portaudio, jack and correct avc
>> > support -- that is very user-visible and would remove a good chunk of
>> > the bugs in my assigned list!
>> >
>> > Cleaning the existing code is pretty important too, as cruft makes it
>> > harder to implement new features.
>> >
>> > Etc
>> >
>>
>> everything has to be done in a 6 months cycle.
>
> Some visible new features from the user point of view:
>
> - Avatars: http://www.ietf.org/rfc/rfc4480.txt especially point 3.12
> - group chat: /!\ DRAFT
> http://tools.ietf.org/html/draft-ietf-sip-uri-list-message-03
> OR
> http://tools.ietf.org/html/draft-ietf-simple-chat-02
> - is composing feature: http://www.ietf.org/rfc/rfc3994.txt (this add
> better interoperabiblity with Pidgin and softwares based on its stack
> for SIMPLE)
> - a log system+search in it, for text messages
> - win32 build (well, not in the 6 months cycle)
> - White and black list (first step in a privacy feature)
> - ZRTP... (I know, not really on our shoulders)

IAX2 (its mentioned under 3 but also mentions a random opal bug).

Peter