Thanks, John. I did a round of updates for this release and expect we can continue do this in subsequent releases.
Bundled dependencies: Commons Lang is at *3.7;* Geode is at 2.6 Log4j is at *2.10.0*; Geode is at 2.8.2 Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final Spring Security is at *5.0.3.RELEASE*; Geode is at 4.2.4.RELEASE. Spring Framework is at *5.0.3.RELEASE*; Geode is at 4.3.14.RELEASE Non-bundled dependencies: AssertJ is at *3.9.1; *Geode is at 3.8.0 Mockito is at *2.15.0*; Geode is at 2.8.9 JSON Path is at *2.4.0*; Geode is at 2.2.0 Tomcat is at *8.5.28*; Geode is at 8.5.9. I haven’t explored the Spring update to see how painful that will be. I do like the dependency management plugin provided by Spring and would like to incorporate that into our build. The log4j update to 2.10.0 had some conflicts with jetty IIRC so I backed off on that one for this release. Anthony > On Mar 6, 2018, at 9:31 AM, John Blum <jb...@pivotal.io> wrote: > > I also noticed that there are several outdated dependency versions yet... > > AssertJ is at *3.9.1; *Geode is at 3.8.0 > Commons Lang is at *3.7;* Geode is at 2.6 > JSON Path is at *2.4.0*; Geode is at 2.2.0 > Log4j is at *2.10.0*; Geode is at 2.8.2 > Mockito is at *2.15.0*; Geode is at 2.8.9 > Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final > Spring Security is at *5.0.3.RELEASE*; Geode is at 4.2.4.RELEASE. > Spring Framework is at *5.0.3.RELEASE*; Geode is at 4.3.14.RELEASE > Tomcat is at *8.5.28*; Geode is at 8.5.9. > > NOTE: the separate spring-tx.version is not needed as it does not differ > from the core Spring Framework. > NOTE: it would probably be easier to import the Spring Framework BOM file > than individual Spring Framework deps. > > These are just want I noticed at a quick glance when comparing to the *Spring > Boot/Spring IO Platform* curated and managed set of dependencies. > > -j > > > > > On Tue, Mar 6, 2018 at 9:06 AM, Anthony Baker <aba...@pivotal.io > <mailto:aba...@pivotal.io>> wrote: > >> Looks like there are some things broken related to serialization filtering >> as well on the release branch: >> >> https://concourse.apachegeode-ci.info/teams/main/pipelines/ >> <https://concourse.apachegeode-ci.info/teams/main/pipelines/> >> release-1.5.0/jobs/DistributedTest/builds/2 <https://concourse >> <https://concourse/>. >> apachegeode-ci.info/teams/main/pipelines/release-1.5.0/ >> <http://apachegeode-ci.info/teams/main/pipelines/release-1.5.0/> >> jobs/DistributedTest/builds/2> >> >> Anthony >> >> >>> On Mar 6, 2018, at 8:57 AM, John Blum <jb...@pivotal.io >>> <mailto:jb...@pivotal.io>> wrote: >>> >>> I don't think this should wait since it affects downstream artifacts >>> (already)... Pivotal GemFire -> PCC. >>> >>> As I stated, I am will have the changes prepared a few hours. This is >>> pretty low risk from Apache Geode's side but is imperative for Spring/PCC >>> users. >>> >>> On Tue, Mar 6, 2018 at 8:40 AM, Alexander Murmann <amurm...@pivotal.io >>> <mailto:amurm...@pivotal.io>> >>> wrote: >>> >>>> John, how much of an issue would it be if the change was added one month >>>> from now? >>>> >>>> On Tue, Mar 6, 2018 at 8:36 AM, John Blum <jb...@pivotal.io >>>> <mailto:jb...@pivotal.io>> wrote: >>>> >>>>> I have 1 addition (planning to submit a PR for review) for the 1.5 >>>> release >>>>> that is imperative for *Spring Data for Apache Geode*, and >> specifically, >>>>> client-side Cluster Configuration Push [1]. >>>>> >>>>> Details to follow soon; will file a ticket in JIRA. >>>>> >>>>> -j >>>>> >>>>> >>>>> [1] >>>>> https://docs.spring.io/spring-data/geode/docs/current/ >>>>> reference/html/#bootstrap-annotation-config-cluster >>>>> >>>>> >>>>> On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker <aba...@pivotal.io> >> wrote: >>>>> >>>>>> Could you make the pipeline public? >>>>>> >>>>>> Anthony >>>>>> >>>>>> >>>>>>> On Mar 5, 2018, at 12:46 PM, Sean Goller <sgol...@pivotal.io> wrote: >>>>>>> >>>>>>> 1.5.0 pipeline is up and running, please take a look at it and let >>>> the >>>>>> list >>>>>>> know if there are problems. >>>>>>> >>>>>>> https://concourse.apachegeode-ci.info/teams/main/pipelines/ >>>>> release-1.5.0 >>>>>>> >>>>>>> On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker <aba...@pivotal.io> >>>>>> wrote: >>>>>>> >>>>>>>> LGTM >>>>>>>> >>>>>>>>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar <sbawas...@pivotal.io >>>>> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Thanks Dave! >>>>>>>>> >>>>>>>>> All, I have created a release branch ( >>>>>>>>> https://github.com/apache/geode/tree/release/1.5.0) Please review. >>>>>>>>> >>>>>>>>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes <dbar...@pivotal.io> >>>>> wrote: >>>>>>>>> >>>>>>>>>> Status on the 3 doc issues: >>>>>>>>>> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done >>>>>>>>>> GEODE-4101: redirect-output - Done >>>>>>>>>> GEODE-3948: client timeout - Done >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar < >>>>>> sbawas...@pivotal.io >>>>>>>>> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> I will take up the release management task for 1.5.0 >>>>>>>>>>> >>>>>>>>>>> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes <dbar...@pivotal.io> >>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Status on the 3 doc issues: >>>>>>>>>>>> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it >>>>> covered >>>>>>>>>>>> GEODE-4101: redirect-output - Dave, in process, on track >>>>>>>>>>>> GEODE-3948: client timeout - Dave, in process. Probably on >>>> track - >>>>>>>> will >>>>>>>>>>>> keep you posted >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker < >>>>> aba...@pivotal.io> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Just checking in as we’re approaching the end of February. >>>> We’ve >>>>>>>>>>>> finished >>>>>>>>>>>>> around 200 issues and enhancements with 3 documentation updates >>>>>> open >>>>>>>>>>> [1]. >>>>>>>>>>>>> Is this a good time for another release? >>>>>>>>>>>>> >>>>>>>>>>>>> Any takers to do the release management tasks for 1.5.0? >>>>>>>>>>>>> >>>>>>>>>>>>> Anthony >>>>>>>>>>>>> >>>>>>>>>>>>> [1] https://issues.apache.org/jira/projects/GEODE/versions/ >>>>>> 12342395 >>>>>>>>>> < >>>>>>>>>>>>> https://issues.apache.org/jira/projects/GEODE/versions/ >>>> 12342395> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> On Feb 7, 2018, at 1:56 PM, Anthony Baker <aba...@pivotal.io> >>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Nice work on getting the 1.4.0 release out the door! Next up >>>> is >>>>>>>>>>> 1.5.0. >>>>>>>>>>>>> Any one want to volunteer for release manager? If you haven’t >>>>> done >>>>>>>>>>> this >>>>>>>>>>>>> before and would like to try, please review [1]. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I’ve been advocating for more frequent releases. I’d love >>>> see a >>>>>>>>>>> March >>>>>>>>>>>>> release—which means we would need to be ready to cut the >>>> release >>>>>>>>>> branch >>>>>>>>>>>> in >>>>>>>>>>>>> early March. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thoughts? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Anthony >>>>>>>>>>>>>> >>>>>>>>>>>>>> [1] >>>>>>>>>>>> https://cwiki.apache.org/confluence/display/GEODE/ >>>>>> Release+Steps?src= >>>>>>>>>>>>> contextnavpagetreemode < >>>>>>>>>>>> https://cwiki.apache.org/confluence/display/GEODE/ >>>>>>>>>>>>> Release+Steps?src=contextnavpagetreemode> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> -John >>>>> john.blum10101 (skype) >>>>> >>>> >>> >>> >>> >>> -- >>> -John >>> john.blum10101 (skype) >> >> > > > -- > -John > john.blum10101 (skype)