Re: Concurrent changelogs - merge or nix?

2019-03-15 Thread Alexander Ploumistos
On Fri, Mar 15, 2019 at 10:24 AM Vít Ondruch wrote: > > I've been there, keeping Ruby .spec file in sync with upstream > development, and my decision was always to drop the detailed changelog > and replace it just with single entry. In the end, in the development > stream, there are many times

Re: Concurrent changelogs - merge or nix?

2019-03-15 Thread Vít Ondruch
I've been there, keeping Ruby .spec file in sync with upstream development, and my decision was always to drop the detailed changelog and replace it just with single entry. In the end, in the development stream, there are many times mentioned just updates to some snapshots, temporary workarounds

Concurrent changelogs - merge or nix?

2019-03-15 Thread Alexander Ploumistos
Hello, For a few months now and in order to help upstreams find bugs and test new features I have been maintaining in copr development versions of a couple of my packages, namely pre-release versions of Molsketch and development snapshots of SciDAVis built against Qt5. At the same time, I have