EPrints Technical Mailing List Archive

Message: #07045

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] EPrints 3.3.16 beta 1

Dear EPrints users and developers.

Here at EPrints HQ in Southampton, we have been investing our time into the progression of the public EPrints release on GitHub (https://github.com/eprints/eprints).
As custodians of the EPrints source code we have been responding to and curating the pull requests, issues and bugs submitted by the community.

We wanted to rationalise what was there and arrange the outstanding issues into groups so they can be better managed and resolved.

With this in mind, there is now a new build of EPrints, version 3.3.16 beta 1.
The current set of outstanding pull requests have been reviewed and applied where applicable. (Except a few more recent ones.)

Issues have been categorised into groups; bugs, enhancements, discussion points.
Then the bugs have been further categorised into groups related to the area of the code they apply to; search, import/export, low level, browse views, multi-lang, interface, bazaar.
The idea being that each area of the code has a manageable set of issues associated with it, rather than having to deal with the whole larger list.

We have made a new tag ‘v3.3.16beta1’ and have built a tar-based distribution.


As users of EPrints, we would very much like you to engage in the testing of this new beta release.

If you would like to assist in the further development of 3.3.16 and are interested in taking on a group of issues, please let us know.

Once we are happy that 3.3.16 is ready, it can be taken out of beta and released publicly on files.eprints.org.

What about 3.4?  While we are still managing 3.4 internally, we are applying any applicable changes from 3.3 as we go, making moving from 3.3 to 3.4 straight forward.

3.4 will be ready for an open public release in 2018.

Justin
EPrints Services