<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Kopano WebApp v3.4.6.1219+713.1">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: [Pkg-giraffe-discuss] Z-push: Q about bug fix</title>
</head>
<body>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;">> </span>But I have no idea why not a version 2.3.8.1 or 2.3.9 is released by z-push.org, or 2.4.0beta2. Maybe some of the guys from Kopano can say something about this.</p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;">At that time it seemed like a good idea to just update the 2.3.8 release, but we also planned to be further with Z-Push 2.4 by now.<br /></span></p>
<p><span style="font-size: 10pt; font-family: Tahoma, Geneva, sans-serif;"><br />Met hartelijke groet, Cordialement, Kind regards,</span></p>
<p><span style="font-size: 10pt; font-family: Tahoma,Geneva,sans-serif;"><strong style="color: #00b3f0;">Felix Bartels</strong> | <strong>Release & QA Manager </strong><br />Tel. +31 (0)15 750 4712 | <a href="https://kopano.com/" style="color: #00b3f0;">www.kopano.com</a></span></p>
<p><span style="font-size: 10pt; font-family: Tahoma,Geneva,sans-serif;"><a href="https://kopano.com/" style="color: #00b3f0;"><img class="fr-fic fr-dii" src="https://i.froala.com/download/babc2086cea542640b21cdd8d45aa7d9ef65982f.jpg?1517824462" border="0" alt="Kopano" width="162" height="38" /></a></span></p>
<p><span style="font-size: 10pt; font-family: Tahoma, Geneva, sans-serif;"><strong>News: </strong>Join us at the <a href="https://kopano.com/upcoming-events/kopano-at-chemnitz-linux-days-2018/" style="color: #00b3f0; font-size: 10pt;">Chemnitz Linux Days 2018</a><br /><strong>Latest whitepaper:</strong> <a href="https://kopano.com/whitepaper-eu-us-cloud-privacy-crash/" style="color: #00b3f0; font-size: 10pt;">EU-US Cloud Privacy Crash</a><br /><strong>Releases:</strong> <a href="https://kopano.com/releases/kopano-releases-in-december-2017/" style="color: #00b3f0; font-size: 10pt;">Kopano Releases in December 2017</a> </span></p>
<blockquote style="border-left: 2px solid #325FBA; padding-left: 5px; margin: 0px 5px;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 10pt;">-----Original message-----<br /><span><strong>From:</strong> Carsten Schoenert <c.schoenert@t-online.de></span><br /><span><strong>Sent:</strong> Tuesday, February 6, 2018 6:46 PM</span><br /><span><strong>To:</strong> pkg-giraffe-discuss@lists.alioth.debian.org</span><br /><span><strong>Subject:</strong> Re: [Pkg-giraffe-discuss] Z-push: Q about bug fix</span><br /><br /></span>
<div>
<pre style="white-space: pre-wrap; word-wrap: break-word;">Hi,<br /><br />Am 06.02.18 um 14:31 schrieb Guido Günther:<br />> I usually track experimental on debian/experimental and merge back on<br />> forth between d/sid and d/experimental.<br /><br />yeah, that's probably the safest way. The assumption for preparing the<br />2.4.0beta version on debian/sid was a expected quickly afterwards<br />release of 2.4.0. But this wasn't happen.<br /><br />O.k. means for the future we should *always* package Betas RCs and<br />Snapshots on debian/experimental.<br /><br />>> I couldn't find any info on that in the maintainers guide. So any pointers<br />>> or a high-quality package that I can use as an example are much appreciated!<br />> <br />> Three solution:<br />> <br />> 1 fix the bug in 2.4 and upload that to d/sid<br />> 2 create a branch and fix it there. d/testing sounds like a reasonable<br />> name although you still upload to unstable.<br />> 3 create the branch only locally and only push the tags not the branch<br />> itself. <br />> <br />> 3.) looks like the cleanest to me if the lifetime of 2.3.8 in<br />> testing/sid is only about one or two months. It gets tedious if you need<br />> to fix more stuff.<br /><br />Normally I'd vote for the first bullet. But the whole thing seems a bit<br />more unneeded complicated than I thought on a first view. Due the<br />changes in kopano-core in 8.5, just released this week on Monday, some<br />changes for z-push 2.3.8 are needed.<br /><br />http://z-push.org/z-push-2-3-8-final-release-update/<br /><br />I've planed to prepare the recent kopano-core version 8.5.0 while this<br />week somehow and upload this to unstable. Then z-push in the testing<br />archive is affected by the needed update of z-push as the website on<br />z-push.org is mentioning. But I have no idea why not a version 2.3.8.1<br />or 2.3.9 is released by z-push.org, or 2.4.0beta2. Maybe some of the<br />guys from Kopano can say something about this.<br />If there is a release of version 2.4.0 planned by z-push I'd do adding a<br />Breaks to kopanocore on z-push (<< 2.3.8-2.1˜) and wait until 2.4.0 can<br />be added to unstable.<br /><br />Otherwise I see a forth possible solution of the branching problem to<br />import the updated version 2.3.8 into debian/sid.<br /><br />Create a new branch debian/experimental based on the tag<br />'debian/2.4.0_beta1-1'.<br />Then revert all commits on debian/sid so you are back on 'debian/2.3.8-2'.<br />Now import the updated version of the upstream source and do the fixing<br />of the bug report on top of the updated debian/sid branch.<br /><br />By this we would have the debian/experimental branch existing for later<br />usage on other upstream versions for the experimental archive but can go<br />on with the current package version in unstable.<br />Not really nice but acceptable I think.<br /><br />-- <br />Regards<br />Carsten Schoenert<br /><br />_______________________________________________<br />Pkg-giraffe-discuss mailing list<br />Pkg-giraffe-discuss@lists.alioth.debian.org<br />http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss</pre>
</div>
</blockquote>
</body>
</html>