Changes between Initial Version and Version 1 of Ticket #8650


Ignore:
Timestamp:
2013-04-30T21:22:36+02:00 (13 years ago)
Author:
Don-vip
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #8650

    • Property Type defect → enhancement

  • Ticket #8650 – Description

    initial v1  
    33thanks for JMapViewer, we're happily using it in the Freeplane project :-)
    44
    5 I am also involved in creating Debian packages for Freeplane and JMapViewer,
    6 and our concern is:
    7 Could you consider making JMapViewer releases with version numbers?  That
    8 would make the Debian packaging easier / more meaningful. Also, we could
    9 use version gaps to express that backwards compatibility could be broken.
     5I am also involved in creating Debian packages for Freeplane and JMapViewer, and our concern is:
     6Could you consider making JMapViewer releases with version numbers?  That would make the Debian packaging easier / more meaningful. Also, we could use version gaps to express that backwards compatibility could be broken.
    107
    11 That would be important for the Freeplane package (and others): When a
    12 Debian packager sees that JMapViewer was updated from say 1.0 to 2.0 (and
    13 he/she finds out after correspondence with you that it is not
    14 backwards-compatible) then he/she can create a new "jmapviewer2" package
    15 that does not interfere with the current "jmapviewer" that is used by
    16 Freeplane.
     8That would be important for the Freeplane package (and others): When a Debian packager sees that JMapViewer was updated from say 1.0 to 2.0 (and he/she finds out after correspondence with you that it is not backwards-compatible) then he/she can create a new "jmapviewer2" package that does not interfere with the current "jmapviewer" that is used by Freeplane.
    179
    1810Thanks!