On Fri, 2005-05-06 at 15:41 +0600, Paul Cadach wrote: > Hello, > > Adam Goryachev wrote: > > On Fri, 2005-05-06 at 14:41 +0600, Paul Cadach wrote: > > > Removing dependencies on zaptel should raise Asterisk as real SOFT switch, > > > > That is just a definition problem.... how do you define "real soft > > switch"?? > > User-space only software which isn't depends on any sort of additional > support from kernel level.
Why?, it is still ALL software... Given that some closed source commercial 'box' may be a soft switch, but then you don't know where the line is between kernel and application... > > Either way, I really don't see that this would be a small enough change > > to say that we should complete this before releasing 1.2. IMHO, the ONLY > > things that should be completed before a 1.2 release are the ones that > > are already mostly done, ie, why wait another 3 months just because xyz > > isn't done yet? plus of course bug fixes. > > Just because software timing was done myself for Asterisk-0.5.0 about 1,5 > years ago, it isn't so complex and could be > ported to CVS-HEAD within one week or faster. Current mechanism to switch > timing between zaptel-based timer and > receiving stream could make such port more easy. Probably, this thing is not > for 1.2 but should be implemented anyway > within 1.x tree. So why didn't you contrib that back when you did it? In fact, why don't you contrib that now? > > I hope we would see a 1.2 release within the next 2 - 3 months (random > > time) because it has been a long time since the last release. At this > > stage, we should be releasing frequantly... once the dev cycle slows, > > and we are mostly just bug fixing with the occassional new feature, then > > a release once per year or even 18mths would be more expected.... > > At least I would see in 1.2 all things already done for CVS-HEAD (and, > probably, not commited due to different reasons), > mostly changes related to expanding functionality, compatibility and > stability of channel drivers and existing > applications. I would think that 1.2 is in fact exactly the same as CVS HEAD. ie, CVS HEAD stops accepting experimental patches/new features over the next 6 weeks, at which point we say CVS HEAD == 1.2.0, and then we fork and start a new CVS HEAD, and continue 1.2.0 which is then CVS STABLE. > Is someone have development plans for next minor and major releases? Is it > publicly available? Generally, it depends on what people are willing to work on, rather than any specific set of features... What are you willing to work on? Mind you, I think the dev-conf probably keeps up with these things, at least looking 1 week into the future at a time :) Regards, Adam -- -- Adam Goryachev Website Managers Ph: +61 2 8304 0000 [EMAIL PROTECTED] Fax: +61 2 9345 4396 www.websitemanagers.com.au _______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
