Thanks, I'll give up on cleaning up my patches then, no point wasting everyones time. I'll make RPM's for anyone who really feels they need this extra polycom support.
I have a couple of other changes to the Polycom plugin that do not require database schema changes (they primarily affect settings and .vm templates), is 4.2 getting closed off altogether or should I still try to get them cleaned up? Is there a mailing list with status/news like this (code freeze coming on date XXX, etc) or is all that sort of info private to Avaya? Thanks, -Eric On Mar 16, 2010, at 1:10 PM, Nair, Arjun (Arjun) wrote: > > >> From: [email protected] >> [mailto:[email protected]] On Behalf Of >> Eric Varsanyi >> >> So is the database schema frozen? (!) I have pending changes >> to the phone book schema; I've been suffering over trying to >> incorporate some integration between the phonebook and the >> polycom plugin that was requested. If the DB schema is now >> frozen I will abandon cleaning up my patches for distinctive >> rings on the polycoms and keep them local. If its not frozen, >> how long do I have? >> > > > Yes, for all intents and purposes, the database schema is frozen. I am > waiting on one more patch to officially close it off. > > Arjun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
