Skip to content

Distribution packages outdated / How to coordinate new releases? #47

@dannyedel

Description

@dannyedel

Hello @kd35a,
Hello @jeeger,

first of all thanks again for helping me with the packaging. I've programmed a bit more since you included dspdfviewer in gentoo and arch and it has a few new features.

I've also done a bit of restructuring and moved (I used git commit --author to commit your lines, I hope thats ok) system-specific installation instructions into the gh-pages branch (which results in a rendered website) to reduce clutter in the sourcecode. While moving, I noticed that the distribution-specific installation instructions may be outdated (at least the gentoo link points to 404). If you could help by checking and - if necessary - updating the instructions, that would be awesome.

However, it's a problem is that we never agreed on a way on how to coordinate new releases. This also applies to @projekter, who succeeded at building windows (!) binaries of dspdfviewer.

I believe the new features added (especially the hyperlinks, and the file-chooser-window when started without a command-line-parameter) justify creating a v1.13 within the next few days. I'd appreciate your help in establishing some kind of "a new release is there" protocol, so this stable release gets propagated to all distributions the software already has a package in.

Please post your ideas here, I hope we can figure something out. (Remember, this is my first-ever open source project, so its all new land for me too and I'm glad to be pointed out to mistakes.)

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions