Re: [OPEN-ILS-GENERAL] Evergreen 3.1 Release Candidate

2018-03-27 Thread Kathy Lussier 

Hi all,

The MassLNC Community demo server is now running the 3.1 Release 
Candidate for those of you who would like to take a look around and see 
what's available.


Access information is available at 
https://wiki.evergreen-ils.org/doku.php?id=community_servers


Kathy


On 03/27/2018 11:04 AM, Daniel Wells wrote:

Hello all,

As of yesterday morning, the Evergreen 3.1 Release Candidate is 
available on the main downloads page:


http://evergreen-ils.org/egdownloads/

While we haven't always been consistent over the years, this release 
candidate is meant to not be a final "beta", but to be a preliminary 
version of the 3.1.0 release.  Other than failures with the actual 
build or late-discovered critical bugs, the 3.1 RC will essentially be 
rebranded as 3.1.0 later this week (pending final feedback from testers).


While we can never get in everything we hope for, I am extremely 
thankful to everyone who made a push in the last few weeks to prepare 
for this release, and am proud of what was accomplished.  Here is a 
list of the 24 improvements since the beta 3 weeks ago:


https://launchpad.net/evergreen/+milestone/3.1-rc

To everyone who tested, commented, and provided code for fixes, thank you!

So, looking ahead a little bit, 3.1.1 is just about 3 weeks away.  If 
we can keep up a similar pace for fixes, we will make a significant 
dent in our number of client bugs sticking around, and in two or three 
releases more, perhaps clear up the most aggravating bugs in that 
backlog entirely.  The most important thing we all can do is continue 
to make (hopefully productive) noise on the bugs which matter most to 
us; a stale bug is often a forgotten bug, but if you champion 
something, people generally will respond.  I know I will!


Sincerely,
Dan


--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Evergreen 3.1 Release Candidate

2018-03-27 Thread Diane Disbro 
Wonderful! Thank you.

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
ddis...@scenicregional.org

On Tue, Mar 27, 2018 at 10:04 AM, Daniel Wells  wrote:

> Hello all,
>
> As of yesterday morning, the Evergreen 3.1 Release Candidate is available
> on the main downloads page:
>
> http://evergreen-ils.org/egdownloads/
>
> While we haven't always been consistent over the years, this release
> candidate is meant to not be a final "beta", but to be a preliminary
> version of the 3.1.0 release.  Other than failures with the actual build or
> late-discovered critical bugs, the 3.1 RC will essentially be rebranded as
> 3.1.0 later this week (pending final feedback from testers).
>
> While we can never get in everything we hope for, I am extremely thankful
> to everyone who made a push in the last few weeks to prepare for this
> release, and am proud of what was accomplished.  Here is a list of the 24
> improvements since the beta 3 weeks ago:
>
> https://launchpad.net/evergreen/+milestone/3.1-rc
>
> To everyone who tested, commented, and provided code for fixes, thank you!
>
> So, looking ahead a little bit, 3.1.1 is just about 3 weeks away.  If we
> can keep up a similar pace for fixes, we will make a significant dent in
> our number of client bugs sticking around, and in two or three releases
> more, perhaps clear up the most aggravating bugs in that backlog entirely.
> The most important thing we all can do is continue to make (hopefully
> productive) noise on the bugs which matter most to us; a stale bug is often
> a forgotten bug, but if you champion something, people generally will
> respond.  I know I will!
>
> Sincerely,
> Dan
>

Re: [OPEN-ILS-GENERAL] Evergreen 3.1 Release Candidate

2018-03-27 Thread Terran McCanna 
Thank you, Dan and everyone who has contributed development and testing and
bug reporting!

Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org


On Tue, Mar 27, 2018 at 11:04 AM, Daniel Wells  wrote:

> Hello all,
>
> As of yesterday morning, the Evergreen 3.1 Release Candidate is available
> on the main downloads page:
>
> http://evergreen-ils.org/egdownloads/
>
> While we haven't always been consistent over the years, this release
> candidate is meant to not be a final "beta", but to be a preliminary
> version of the 3.1.0 release.  Other than failures with the actual build or
> late-discovered critical bugs, the 3.1 RC will essentially be rebranded as
> 3.1.0 later this week (pending final feedback from testers).
>
> While we can never get in everything we hope for, I am extremely thankful
> to everyone who made a push in the last few weeks to prepare for this
> release, and am proud of what was accomplished.  Here is a list of the 24
> improvements since the beta 3 weeks ago:
>
> https://launchpad.net/evergreen/+milestone/3.1-rc
>
> To everyone who tested, commented, and provided code for fixes, thank you!
>
> So, looking ahead a little bit, 3.1.1 is just about 3 weeks away.  If we
> can keep up a similar pace for fixes, we will make a significant dent in
> our number of client bugs sticking around, and in two or three releases
> more, perhaps clear up the most aggravating bugs in that backlog entirely.
> The most important thing we all can do is continue to make (hopefully
> productive) noise on the bugs which matter most to us; a stale bug is often
> a forgotten bug, but if you champion something, people generally will
> respond.  I know I will!
>
> Sincerely,
> Dan
>

[OPEN-ILS-GENERAL] Evergreen 3.1 Release Candidate

2018-03-27 Thread Daniel Wells 
Hello all,

As of yesterday morning, the Evergreen 3.1 Release Candidate is available
on the main downloads page:

http://evergreen-ils.org/egdownloads/

While we haven't always been consistent over the years, this release
candidate is meant to not be a final "beta", but to be a preliminary
version of the 3.1.0 release.  Other than failures with the actual build or
late-discovered critical bugs, the 3.1 RC will essentially be rebranded as
3.1.0 later this week (pending final feedback from testers).

While we can never get in everything we hope for, I am extremely thankful
to everyone who made a push in the last few weeks to prepare for this
release, and am proud of what was accomplished.  Here is a list of the 24
improvements since the beta 3 weeks ago:

https://launchpad.net/evergreen/+milestone/3.1-rc

To everyone who tested, commented, and provided code for fixes, thank you!

So, looking ahead a little bit, 3.1.1 is just about 3 weeks away.  If we
can keep up a similar pace for fixes, we will make a significant dent in
our number of client bugs sticking around, and in two or three releases
more, perhaps clear up the most aggravating bugs in that backlog entirely.
The most important thing we all can do is continue to make (hopefully
productive) noise on the bugs which matter most to us; a stale bug is often
a forgotten bug, but if you champion something, people generally will
respond.  I know I will!

Sincerely,
Dan