[Pkg-giraffe-discuss] Z-push: Q about bug fix

[Guido Günther]

Hi Felix,
On Wed, Feb 07, 2018 at 09:25:02AM +0100, Felix Bartels wrote:
> > 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.
> 
> 
> 
> 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.

This reminds me of

    https://fosdem.org/2018/schedule/event/how_to_make_package_managers_cry/

Please don't do this.
Cheers,
  -- Guido

> 
> 
> Met hartelijke groet, Cordialement, Kind regards,
> 
> Felix Bartels | Release & QA Manager 
> Tel. +31 (0)15 750 4712 | www.kopano.com
> 
> 
> News: Join us at the Chemnitz Linux Days 2018
> Latest whitepaper: EU-US Cloud Privacy Crash
> Releases: Kopano Releases in December 2017 
> 
> -----Original message-----
> From: Carsten Schoenert <c.schoenert at t-online.de>
> Sent: Tuesday, February 6, 2018 6:46 PM
> To: pkg-giraffe-discuss at lists.alioth.debian.org
> Subject: Re: [Pkg-giraffe-discuss] Z-push: Q about bug fix
> 
> 
> Hi,
> 
> Am 06.02.18 um 14:31 schrieb Guido Günther:
> > I usually track experimental on debian/experimental and merge back on
> > forth between d/sid and d/experimental.
> 
> yeah, that's probably the safest way. The assumption for preparing the
> 2.4.0beta version on debian/sid was a expected quickly afterwards
> release of 2.4.0. But this wasn't happen.
> 
> O.k. means for the future we should *always* package Betas RCs and
> Snapshots on debian/experimental.
> 
> >> I couldn't find any info on that in the maintainers guide. So any pointers
> >> or a high-quality package that I can use as an example are much appreciated!
> > 
> > Three solution:
> > 
> >  1 fix the bug in 2.4 and upload that to d/sid
> >  2 create a branch and fix it there. d/testing sounds like a reasonable
> >    name although you still upload to unstable.
> >  3 create the branch only locally and only push the tags not the branch
> >    itself. 
> > 
> > 3.) looks like the cleanest to me if the lifetime of 2.3.8 in
> > testing/sid is only about one or two months. It gets tedious if you need
> > to fix more stuff.
> 
> Normally I'd vote for the first bullet. But the whole thing seems a bit
> more unneeded complicated than I thought on a first view. Due the
> changes in kopano-core in 8.5, just released this week on Monday, some
> changes for z-push 2.3.8 are needed.
> 
> http://z-push.org/z-push-2-3-8-final-release-update/
> 
> I've planed to prepare the recent kopano-core version 8.5.0 while this
> week somehow and upload this to unstable. Then z-push in the testing
> archive is affected by the needed update of z-push as the website on
> z-push.org is mentioning. 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.
> If there is a release of version 2.4.0 planned by z-push I'd do adding a
> Breaks to kopanocore on z-push (<< 2.3.8-2.1˜) and wait until 2.4.0 can
> be added to unstable.
> 
> Otherwise I see a forth possible solution of the branching problem to
> import the updated version 2.3.8 into debian/sid.
> 
> Create a new branch debian/experimental based on the tag
> 'debian/2.4.0_beta1-1'.
> Then revert all commits on debian/sid so you are back on 'debian/2.3.8-2'.
> Now import the updated version of the upstream source and do the fixing
> of the bug report on top of the updated debian/sid branch.
> 
> By this we would have the debian/experimental branch existing for later
> usage on other upstream versions for the experimental archive but can go
> on with the current package version in unstable.
> Not really nice but acceptable I think.
> 
> -- 
> Regards
> Carsten Schoenert
> 
> _______________________________________________
> Pkg-giraffe-discuss mailing list
> Pkg-giraffe-discuss at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss