[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Upgrading from 3.0



Hi Gianluca,

Here are some wiki pages may be of use:

https://wiki.eprints.org/w/Upgrading_EPrints_3_versions (it says 
deprecated but this is more to do with 3.0 and 3.1 being really quite 
old now)

https://wiki.eprints.org/w/Upgrading

 ??? - https://wiki.eprints.org/w/Upgrading_from_3.1

 ??? - https://wiki.eprints.org/w/Upgrading_from_3.2

I have been writing some instructions for 3.3 to 3.4 upgrades but not 
really ready to make publicly available yet, as they have a lot of 
repository specific references.? I don't think you need to worry about 
upgrading to 3.4 immediately.? I suspect the majority of repositories 
will take a good few months if not a year or more before upgrading to 3.4.

EPrints 3.4 is somewhat of a tidying up exercise to provide a better 
basis for different 'flavours' of EPrints, allowing you to run a 
standard publications repository or a much more lightweight EPrints that 
can be made bespoke without all the publication features you might not 
need.? In some cases an upgrade from EPrints 3.3 to 3.4 may just require 
the addition of a couple of files and no modification to existing config 
files in the archives cfg directory and subdirectories.? However, the 
instructions I have been working on will be more comprehensive, as it 
needs to cover a wide variety of bespoke changes that a particular 
repository may have made.

Regards

David Newman


On 08/05/2018 09:48, Christopher Gutteridge wrote:
> Someone on the current team may be more accurate for 3.3 versioning, but
> roughly speaking, the patch releases (eg 3.0.1 to 3.0.2) just add minor
> features and bugfixes without changing how things work. The "minor"
> releases eg. 3.3 to 3.4 will change things a bit and may deprecate or
> turn off features, requiring work to update your configuration. The
> major releases 1 -> 2 -> 3 were entire rewrites requiring you to create
> a brand new install and migrate the data over.
>
> With this in mind, going from 3.0 to 3.4 is actually going to be going
> 3.0->3.1, 3.1->3.2, 3.2->3.3, 3.3->3.4
>
> You can do the software upgrade in one hit, BUT you should work through
> any tasks required for every single minor update. It's going to be a bit
> of work, but you've not upgraded it since Twitter was launched...
>
>
>
> On 08/05/2018 09:21, Gianluca Sforna wrote:
>> On Tue, May 8, 2018 at 8:53 AM, Yuri <yurj at alfa.it> wrote:
>>> There's a specific upgrade guide frmo 2.3 to 3.0 in eprints.org:
>>>
>>> http://files.eprints.org/256/
>>>
>>> did you try it?
>> My migration is from 3.0 (specifically, VERSION says 3.0.5-rc-1) so
>> this should not be needed.
>>
>> Anyway, I managed to have at least a working archive by creating a new
>> archive (epadmin create), then moving over the files in
>> documents/disk0 and finally performing the 'epadmin upgrade' command.
>>
>> However, I do not know eprints well enough to understand if this is
>> going to cause issues later. For sure, I am still missing the template
>> customization they made to the old archive pages.
>> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>> *** Archive: http://www.eprints.org/tech.php/
>> *** EPrints community wiki: http://wiki.eprints.org/
>> *** EPrints developers Forum: http://forum.eprints.org/
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/


---
This email has been checked for viruses by AVG.
http://www.avg.com