Thanks for getting the conversation rolling, Jeff! To me, 4.0 also implies (intentional) breaking changes. Removing the XUL client <https://bugs.launchpad.net/evergreen/+bug/1928126>, perhaps, or the dojo interfaces that have Angular or AngularJS equivalents, or various other things that we've deprecated but never removed?
El mar, 8 jul 2025 a la(s) 4:22 p.m., Jeff Davis via Evergreen-dev ( [email protected]) escribió: > We've been talking about calling our next major release Evergreen 4.0, > rather than 3.16. > > Is there a list of features that we want to include in a 4.0 release? > Should we hold off on bumping the version number to 4.0 until those > features are ready? > > Some candidates for "features that warrant going to 4.0": > - Making Angular circ the standard circ UI, rather than experimental. My > understanding is that we don't expect that to happen in the next release. > - Merging OpenSRF into Evergreen (LP#2032835). We were waiting to replace > ejabberd with Redis before doing that; Redis is now supported in Evergreen, > but I don't know if anyone has revisited merging OpenSRF into EG since then. > - There are a number of bugs targeted to "4.0-beta" in Launchpad, but > AFAIK they are just targeting the next major release, whether it's called > 4.0 or not. > > Any opinions? I would prefer to reserve "4.0" for a release that is > somehow "more" than just the next major release, but I recognize that > version numbering is basically arbitrary. > -- > Jeff Davis > BC Libraries Cooperative > _______________________________________________ > Evergreen-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Evergreen-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
