On 2015-03-15, at 22:53 , Jayaraj JR wrote:
> As of now, we are already on Evergreen 2.6.4 version. In this context what
> would be best way to upgrade to 2.7 series. Can we use
> the upgrade script 2.6.3 to 2.7.0 here. If not what modifications are
> necessary ?. If we upgrade to 2.6.7, will
Hello,
We have been keenly observing the discussion about the upgrade of Evergreen
ILS from version 2.6.4 to 2.7 series.
The upgrade would be simple and easier if we are on the version 2.6.3 as
the Evergreen 2.7 provides direct step for upgrade from
2.6.3 to 2.7.0.
As of now, we are already on Ev
some sort of upgrade mechanism that just aggregates
>> > and runs each of the constituent scripts? What is the reasoning behind
>> > stringing them into the longer monolithic scripts since running through the
>> > numbered scripts provides the same outcome?
>> >
>>
Hi,
On Fri, Mar 13, 2015 at 4:22 PM, Chris Sharp
wrote:
> Yeah, I can see the advantage of the full rollback. I wonder if the
> wrapper/controller script I'm imagining (and Mike mentions in his "steps to
> make this actually happen" response could have some sort of rollback option
> (though I k
Galen,
> - The monolithic scripts allow for consolidating multiple point updates
> into a set of statements that run more quickly. Arguably this is more of a
> potential for efficiency than something that has always been taken
> advantage of -- but sometimes, it has.
> - Of more import, since the
s since running through the
> numbered scripts provides the same outcome?
> >
> > (Asking the full list, not Galen specifically).
> >
> > ----- Original Message -
> >> From: "Galen Charlton"
> >> To: "Evergreen Discussion Gro
riginal Message -
> From: "Mike Rylander"
> To: "Evergreen Discussion Group"
> Sent: Friday, March 13, 2015 4:07:51 PM
> Subject: Re: [OPEN-ILS-GENERAL] Upgrade Script for 2.6.4 to 2.7
>
> Chris,
>
> That's what I've advocated for in the p
Thanks for the quick and detailed response, Ben.
> While the numbers for upgrade scripts are purely sequential in master,
> they are not complete and sequential for upgrades in release branches,
> at least once you start talking maintenance releases since we do not
> always backport every upgrade
Hi,
On Fri, Mar 13, 2015 at 3:47 PM, Chris Sharp
wrote:
> Couldn't we develop some sort of upgrade mechanism that just aggregates
> and runs each of the constituent scripts? What is the reasoning behind
> stringing them into the longer monolithic scripts since running through the
> numbered scr
ot;Evergreen Discussion Group" <
> open-ils-general@list.georgialibraries.org>
> > Sent: Friday, March 13, 2015 3:31:33 PM
> > Subject: Re: [OPEN-ILS-GENERAL] Upgrade Script for 2.6.4 to 2.7
> >
> > Hi,
> >
> > On Fri, Mar 13, 2015 at 1:51 PM,
the reasoning behind
>> stringing them into the longer monolithic scripts since running through the
>> numbered scripts provides the same outcome?
>>
>> (Asking the full list, not Galen specifically).
>>
>> ----- Original Message -
>>> From: "G
t Galen specifically).
>
> - Original Message -
>> From: "Galen Charlton"
>> To: "Evergreen Discussion Group"
>> Sent: Friday, March 13, 2015 3:31:33 PM
>> Subject: Re: [OPEN-ILS-GENERAL] Upgrade Script for 2.6.4 to 2.7
>>
&g
?
(Asking the full list, not Galen specifically).
- Original Message -
> From: "Galen Charlton"
> To: "Evergreen Discussion Group"
> Sent: Friday, March 13, 2015 3:31:33 PM
> Subject: Re: [OPEN-ILS-GENERAL] Upgrade Script for 2.6.4 to 2.7
>
> Hi,
>
Hi,
On Fri, Mar 13, 2015 at 1:51 PM, Lazar, Alexey Vladimirovich <
alexey.la...@mnsu.edu> wrote:
>
> Since an Open-ILS/src/sql/Pg/version-upgrade script is a subset of several
> specific Open-ILS/src/sql/Pg/upgrade/ scripts, is there any harm in
> just applying the scripts separately, in
Hello.
On 2015-03-07, at 12:20 , Ben Shum wrote:
> So the upgrade scripts are intended to be done sequentially as written
> due to certain limitations in the build process of Evergreen currently
> (this is still under community discussion). So unfortunately, if
> you're already on 2.6.4, then y
Hello,
So the upgrade scripts are intended to be done sequentially as written
due to certain limitations in the build process of Evergreen currently
(this is still under community discussion). So unfortunately, if
you're already on 2.6.4, then you may have some small edits necessary
to perform th
16 matches
Mail list logo
