[OPEN-ILS-DEV] Thoughts on Evergreen 3.6

[Driscoll, Martha]

Another negative of waiting for a large release in the spring is the
complexity and time needed to upgrade production servers.  Some database
updates can take a while on production data and there's only so many hours
available if you want to upgrade off hours.

I love the idea of a release in the fall that concentrates on current pull
requests.  There are a number of launchpad bugs that I incorporate when I
do an upgrade because we need the functionality or fix.  Again, it would
simplify upgrades to get these finally committed.

Martha Driscoll, Systems Manager
North of Boston Library Exchange
www.noblenet.org




On Thu, Jun 18, 2020 at 2:28 PM Blake Henderson <blake at mobiusconsortium.org>
wrote:

> All,
>
> I like the idea of keeping the twice-per-year tempo. Likewise, it sounds
> like it can still be a feature-rich release even with the squeezed
> development time. So I am sold! Though, skipping the October date in favor
> of getting back on track in the Spring of 2021 doesn't seem like the end of
> the world either :) - Perhaps a negative would be that it would be a "huge"
> amount of changes which in-turn could have a larger impact on bug reports
> for those that adopt it.
>
> -Blake-
> Conducting Magic
> MOBIUS
>
>
> On 6/18/2020 11:52 AM, Galen Charlton wrote:
>
> Hi,
>
> Now that Evergreen 3.5.0 is nearly out the door, I have some thoughts on
> planning for 3.6.
>
> First, I suggest that we plan on a general release in October, though
> perhaps more like the middle of the month rather than than the beginning of
> it. Doing so would allow us to keep to a twice-a-year tempo and not lose
> momentum like we might if we skipped the fall release entirely this year.
> Pushing general release into November or December would run into the winter
> holidays.
>
> An October release would of course mean a shorter cycle, but I think we
> can actually work that to our advantage by having the focus of 3.6 be
> catching up with the backlog of pull requests, particularly ones
> implementing new features.  At the moment, there are 52 pull requests that
> are signed off and 155 that are not signed off; a release that did nothing
> but merge a good chunk of these would nonetheless be a featureful one
> indeed.
>
> I'm not suggesting that 3.6 be just about the backlog; I know that Bill is
> suggesting that the Angular catalog become the default and that Equinox is
> planning on putting out big branches for the Angular acquisitions work over
> the next few weeks. However, an emphasis on reducing the backlog would both
> tidying up the bug list and deal with the fact that some features have been
> waiting months or years for review and merging.
>
> What do folks think? And are there people interested in proposing to
> become RM or co-RM for this cycle?
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Implementation and Services Manager
> Equinox Open Library Initiative
> phone:  1-877-OPEN-ILS (673-6457)
> email:  gmc at equinoxInitiative.org
> web:  https://equinoxInitiative.org
> direct: +1 770-709-5581
> cell:   +1 404-984-4366
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20200619/dc9ac2b4/attachment-0001.html>