+1 It should be pretty easy to clone the current pipeline for the 1.4.0 release branch.
I’ll plan to update the Jenkins jobs to run the `build` and `updateArchives` tasks since those still have value. Anthony > On Jan 4, 2018, at 5:03 PM, Alexander Murmann <amurm...@pivotal.io> wrote: > > The Concourse pipeline seems much more reliable at this point and the > pipelines should be providing equivalent test coverage. Given that, are > there any reasons to not deprecate Jenkins? > > On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh <jhu...@pivotal.io> wrote: > >> Hi Swapnil, >> >> GEODE-4140 was just marked for 1.4. I think part of GEODE-4140 should be >> fixed because the process.ClusterConfigurationNotAvailableException should >> probably be reinstated. If others don't think it's needed then feel free >> to remove the fix tag. >> >> -Jason >> >> On Thu, Jan 4, 2018 at 4:38 PM Dan Smith <dsm...@pivotal.io> wrote: >> >>> Our process up to this point has been to not ship until the jenkins >> builds >>> on the release branch pass. We've been experimenting with concourse in >>> parallel with jenkins, but the jenkins builds on develop at least are >> still >>> pretty messy. How are we going to ship this release? Should both be >>> passing? >>> >>> -Dan >>> >>> On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar <sbawas...@pivotal.io> >>> wrote: >>> >>>> Since all the issues tagged for 1.4.0 release >>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa? >>>> rapidView=92&projectKey=GEODE&view=planning&selectedIssue= >>>> GEODE-3688&versions=visible&selectedVersion=12341842> >>>> have been addressed, I went ahead and created a release branch for >> 1.4.0. >>>> >>>> Can someone please update the concourse pipelines to pick up this >> release >>>> branch? >>>> >>>> Thanks! >>>> >>>> >>>> On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar <sbawas...@pivotal.io >>> >>>> wrote: >>>> >>>>> Well, making sure that the JIRA's status is up-to-date and removing >> the >>>>> 1.4.0 version tag if the fix can wait for a later release. >>>>> >>>>> On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge < >>>> mdo...@pivotal.io> >>>>> wrote: >>>>> >>>>>> What sort of update? I know that GEODE-4010 has a PR that's awaiting >>>>>> review and merge. >>>>>> >>>>>> Sarge >>>>>> >>>>>>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar <sbawas...@pivotal.io >>> >>>>>> wrote: >>>>>>> >>>>>>> I would like to volunteer as a release manager. >>>>>>> Currently there are 14 issues that are marked for 1.4.0. If you >> are >>>>>> working >>>>>>> on any of these, can you please update the JIRA? >>>>>>> >>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa? >>>> rapidView=92&projectKey=GEODE&view=planning&selectedIssue= >>>> GEODE-3688&versions=visible&selectedVersion=12341842 >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker <aba...@pivotal.io> >>>>>> wrote: >>>>>>> >>>>>>>> Bump. Any volunteers? If not, I’ll do this. >>>>>>>> >>>>>>>> Anthony >>>>>>>> >>>>>>>> >>>>>>>>> On Nov 22, 2017, at 1:48 PM, Anthony Baker <aba...@pivotal.io> >>>> wrote: >>>>>>>>> >>>>>>>>> We released Geode 1.3.0 at the end of October. Our next release >>>> will >>>>>> be >>>>>>>> 1.4.0. Questions: >>>>>>>>> >>>>>>>>> 1) Who wants to volunteer as a release manager? >>>>>>>>> 2) What do we want to include in the release? >>>>>>>>> 3) When do we want to do this? >>>>>>>>> >>>>>>>>> IMO, let's should shoot for an early Dec release. >>>>>>>>> >>>>>>>>> Anthony >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>> >>> >>
