Re: Preparing next m-pmd-p release

Hi Andreas, On 01/05/18 19:55, Andreas Dangel wrote: Hi Karl Heinz, I can do it. Then, the build should be good again :) It should...and just go on... Kind regards Karl Heinz Marbaise Regards, Andreas Am 01.05.2018 um 19:50 schrieb Karl Heinz Marbaise: Hi Andreas, based on having integr

Re: Preparing next m-pmd-p release

Hi Karl Heinz, I can do it. Then, the build should be good again :) Regards, Andreas Am 01.05.2018 um 19:50 schrieb Karl Heinz Marbaise: > Hi Andreas, > > based on having integrated the branches MPMD-252 and MNGSITE-332 into > master you can also remove the appropriate branches... > > Should I

Re: Preparing next m-pmd-p release

Hi Andreas, based on having integrated the branches MPMD-252 and MNGSITE-332 into master you can also remove the appropriate branches... Should I integrate the branch MPMD-262 into master ? Or you would you prefer to do it ? Kind regards Karl Heinz Marbaise On 01/05/18 17:50, Andreas Dangel

Re: Preparing next m-pmd-p release

Hi Andreas, just fine go ahead... Kind regards Karl Heinz Marbaise On 01/05/18 19:32, Karl Heinz Marbaise wrote: Hi Andreas, On 01/05/18 17:50, Andreas Dangel wrote: Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, t

Re: Preparing next m-pmd-p release

Hi Andreas, On 01/05/18 17:50, Andreas Dangel wrote: Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, they should not be included? If not, I'm going to merge/pick them. * Upgrade parent to 31 [MPMD-252] * Change downloa

Re: Preparing next m-pmd-p release

Am 2018-05-01 um 17:50 schrieb Andreas Dangel: Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, they should not be included? If not, I'm going to merge/pick them. * Upgrade parent to 31 [MPMD-252] * Change download templ

Preparing next m-pmd-p release

Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, they should not be included? If not, I'm going to merge/pick them. * Upgrade parent to 31 [MPMD-252] * Change download template to not use md5 anymore [MNGSITE-332] Regards