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

Damien Sandras a écrit :
Le mercredi 17 septembre 2008 à 15:05 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
Le mercredi 17 septembre 2008 à 13:39 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
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

(*) cleaning of existing code :

(*) better engine :

(*) gstreamer :

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.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]