From: [email protected]
[mailto:[email protected]] On Behalf Of Douglas Hubler
Sent: Thursday, May 12, 2011 1:38 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 has been
updated

 

On Thu, May 12, 2011 at 4:29 PM, Matthew Kitchin (public/usenet)
<[email protected]> wrote:
> On 5/12/2011 3:20 PM, Douglas Hubler wrote:
>>> I
>>> do wonder why they are not archived in another repo (the previous
4.4.0-192
>>> packages. It makes the onus on the superadmin to have saved it as its no
>>> longer available.
>> Added items #6 to release policy...
>> http://wiki.sipfoundry.org/display/sipXecs/Bug+Fix+Release+Policy
> Is it remotely feasible to have the patch process store a copy of these
> before they are upgraded? If not by default, then maybe as an option?

I'm willing to come up with easy instructions for how folks can keep
local copies.

re:ISO
I might change my mind, but ISO are not updated with new RPMs.  People
would need to be in the habit of updating after installing if they
want the latest fixes.  rationale i gave last time: i'm not uploading
a binary that wasn't tested, and I'm not testing ISOs for every fix.
-----------------------------------------------------

I know this entails more work, but for sanity sake, would it not make sense
to have a log kept that shows all patches that are applied to a given
release.  From a troubleshooting standpoint, it would be nice to be able to
open a file that shows what has been installed since the last release.   Is
there a possibility of creating a Patch.log file that get placed into a
specific folder to show what patches are applied, when the patches are
installed, that gets moved during a complete software update.

If you look at many of the other products on the market, they will show you
a list of applied patches, it's the only way to know what is running on the
system, versus what is required to run on the system.

 

 

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to