Attached are the release notes, if you are not affected by any of the
issues, you do not have to update.
BTW: I created this issue to improve this release announcement process
http://track.sipfoundry.org/browse/XX-8654
commit b498ba8a58806b16dbe356bca7356e0df3087eb7
Author: Douglas Hubler
Considering these are optional will these be separate RPM files?
For example:
SipXmodule-XX--4.2.1.patch.rpm
On Tue, Aug 17, 2010 at 10:41 AM, Douglas Hubler dhub...@ezuce.com wrote:
Attached are the release notes, if you are not affected by any of the
issues, you do not have to update.
On Tue, Aug 17, 2010 at 12:09 PM, Jim Canfield jcanfi...@emstar.com wrote:
Considering these are optional will these be separate RPM files?
For example:
SipXmodule-XX--4.2.1.patch.rpm
no, patches is a bit of a misnomer, these are all new rpms files. You
system as a whole is patched
On Tue, Aug 17, 2010 at 12:51 PM, Jim Canfield jcanfi...@emstar.com wrote:
On Tue, Aug 17, 2010 at 11:28 AM, Douglas Hubler dhub...@ezuce.com wrote:
On Tue, Aug 17, 2010 at 12:09 PM, Jim Canfield jcanfi...@emstar.com
wrote:
Considering these are optional will these be separate RPM files?
Which makes me ask... INSTEAD of using sipxconfig to perform an update,
how about an option to PREPARE SYSTEM FOR UPDATE.
- Full backup in separate folder that won't be purged in 30 days or
whatever.
- Snapshot.
- etc.
Then you can do an update/upgrade from the CLI. Easier to force
