On Wed, Jun 9, 2010 at 9:17 AM, Alfred Campbell <[email protected]> wrote: > When we released 4.2 we were in the process of coming up with a new > improved repository structure. This makes it easier for the developers > to build
Just so i can understand what this change is, will it be easier for avaya developers or non-avaya developers? Are you changing the build scripts in addition to changing the address of the repository? Will it be possible for non-avaya employees to get commit access? Please explain in as much detail as you can by "easier to build" for the benefit of the entire developer community. > however the side effect is it mingles in Avaya/Nortel software > with the code we normally contribute to open source. that's like saying side effect of stabbing oneself is bleeding to death. ;) if you go with a dual-upstream model, will avaya developer commit to main that is shared, or periodically merge into main from an internal repo. I ask so i that i can understand the route of any patches that are submitted, e.g. submitted patch -> committed to internal repo --> bulk merged into sipxecs repo _______________________________________________ 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/
