Joe Attardi wrote:
> Damian Krzeminski wrote:
>> "Minor version upgrade" - from 4.0.2 to 4.0.3 (but not to 4.2)
>> "Major version upgrade" - from 4.0 to 4.2
> 
> What about updating the operating system packages as we discussed in the 
> meeting? Are we still going to support that?
> 
> If so, we should probably keep them separate - i.e. there are two 
> categories of updates - "sipXecs/SCS updates" and "Operating system 
> updates".
> 

Quite frankly I do not think that Helen wants to do OS system upgrades with
that.

There are all kinds of reasons why it's not a good idea.
We (as in sipXecs developers) have absolutely no control on what will be
upgraded and how it'll affect running version of sipx. What if we upgrade
to some kernel version that breaks something. What if a new version of tar
utility breaks restore scripts (it actually happened once).

I would think that we need to restrict ourselves to upgrading sipXecs
related components. If we need a newer version of some OS component we can
always add a specific dependency on it in our RPM and it will get upgraded
as dependency.

Again - my opinion only - I actually do not know Helen all that well.
D.


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to