El Dijous, 17 de juliol de 2014, a les 14:53:13, Cornelius Schumacher va escriure: > On Thursday 17 July 2014 01:19:45 Albert Astals Cid wrote: > > * My suggestion is call it "KDE Applications $YEAR.$MONTH", i.e. if we > > keep > > > > with the 4 month schedule next release would be "KDE Applications 14.12" > > and next-next "KDE Applications 15.04". It has a small problem if we slip > > the release from one month to another the name changes, but we just have > > to > > plan all the releases early in the release month so that even if it slips > > it still falls inside the month. > > For clarification: Your suggestion is to name the release itself "KDE > Applications $YEAR.$MONTH", no all the applications, which are part of the > release. So tarball names, version numbers in about dialogs, etc. would > continue to have the known version schema 4.xx or 5.xx depending on what > version of the platform/frameworks they are using. The release name would be > a pure promo thing. > > Is this correct?
Tarball version numbers and application version numbers have never been in sync. Tarball version number reflects to which "Applications release" the tarball belongs, while the application version number is something the developer decides (and sometimes they decide to sync up with the "Applications release" number). Examples: okular-4.13.3.tar.xz contains Okular 0.19.3 kate-4.13.3.tar.xz contains Kate 3.13.3 konsole-4.13.3.tar.xz contains Konsole 2.13.2 kdepim-4.13.3.tar.xz contains KMail 4.13.3 I would like to follow the same in the "KDE Applications 14.12 release" Examples: okular-14.12.0.tar.xz contains Okular 0.21.0 kate-14.12.0.tar.xz contains Kate 3.15.0 konsole-14.12.0.tar.xz contains Konsole 2.15.0 kdepim-14.12.0.tar.xz contains KMail 5.0.0 Cheers, Albert >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
