On Fri, Sep 17, 2021 at 9:53 PM William A Rowe Jr <wr...@rowe-clan.net> wrote: > > We have much activity on apr-util-1.7.0 but no release actions for > some time now. > There are very minor changes to 1.6.x branch. > > Do we want to release 1.7.0, or only a 1.6.x bump? > Or do we want to do both? Are we ready and are the API changes considered? > > All observations and feedback on apr-util releases encouraged...
I tried to align apr-util 1.6.x and 1.7.x w.r.t. "bug fixes" in case we want to release both, but I think that it's not necessarily worth it. Looking at the diffs between the two here is what I found: * Build with Mariadb not in 1.6.x: - http://svn.apache.org/viewvc?rev=1872061&view=rev * Build with libxml2/expat work in 1.7.x only (I think 1.6.x would want it too?): - http://svn.apache.org/viewvc?rev=1854603&view=rev - http://svn.apache.org/viewvc?rev=1880287&view=rev (Also on the xml side still, do we want Windows' xmllite work in 1.7.x? Ivan?) * The crypto PRNG and Digests are new to 1.7.x (not 1.6.x material per our compat rules). I'm not sure that 1.6.x is fine with openssl-1.1(.1)+, OPENSSL_init_crypto() is in 1.7.x only (we probably want these changes in both). * apr_dbm_driver_t and apr_dbm_get_driver() are new to 1.7.x (not 1.6.x material per our compat rules). * apu_dso_init/load() fixes w.r.t. global pool scope in 1.7.x only (I think we'd want to align here too). So if we want to release both, should we look at the above points that can align? Regards; Yann.
