I apologize for moving builds around as much as i am, i'm trying to
preserve migration paths where i can and create a system that usable
going forward. On that note, i created a couple pages on how I would
like to see releases and source code managed.

  http://wiki.sipfoundry.org/display/sipXecs/Source+Code+Branch+Strategy
  http://wiki.sipfoundry.org/display/sipXecs/Version+Numbers

Active members of the build team ok-ed the change.

   http://wiki.sipfoundry.org/display/sipXecs/Release+Engineering+Team

Thanks goes to Russ Herrold for suggesting the versioning scheme that
will both quickly identify instable builds and ensure no one
accidentally installed a build that is deemed less stable.  Hopefully
I captured his suggestion correctly.  I have not worked out the
command to go from a production release to a less stable release on
all sipx components, but I'll work that out.  Installing fresh is not
a problem.

First build for centos with new numbering scheme can be found by using
this repo file.

   http://download.sipfoundry.org/pub/sipXecs/sipxecs-centos-snapshot.repo

I have not built the ISO yet.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to