5 ms·

Interesting seeing a new release shortly after 21.07 , since 21.07 has been in development for years? (afaik), until it finally came out. Does anyone know if so

Interesting seeing a new release shortly after 21.07 , since 21.07 has been in development for years? (afaik), until it finally came out. Does anyone know if somebody took over maintenance or they switched their internal processes to speed up development? or is it just that 21.07 has been such a huge chunk of work that it simply took long, and now we could expect more frequent releases? in any case, kudos to the continued development, this is one of my favorite pieces of software, no web bloat, just a very solid piece of engineering of a native application. I'd very much like to see more of these, instead of turning nowadays everything into a web app, I really find them unbearable most often, to the point that I even choose to use native software that's no longer maintained, if there's no other alternative to an electron/web resource hog, which are as far from snappiness as possible.

themitigating 4y ago
The versioning 7-zip only rule is to increase the value, there is no system
- fomine3 4y ago
  YY.increment? Looks reasonable versioning scheme for application.
  - pvillano 4y ago
    esp w/ jetbrains and their yearly (?) releases that appear to add whatever features they finished since the last release. I've also seen yyyy.increment.build
  - themitigating 4y ago
    It went from 4.65 to 9.04. Then later it jumped from 9.38 to 15.05. Then 16.02,16.03,16.04 , 17.00, 17.01, 18.00 These jumps don't correlate with major changes and major versions
emn13 4y ago
I'm not sure there's a "they" here; IIRC this is and always has been one man project by Igor Pavlov, who incidentally didn't just write the software, but also created the LZMA algorithm which has had an absurdly long run as one of the world-leading general purpose compression algorithms.
SECProto 4y ago
Looking back at this version history [1], there was perviously a gap of 3.5 years between releases (2011-2014). Skimming through the discussion forums, the 2.5yr gap between 19.00 and 21.07 was filled with a number of alpha and beta releases, eg 20.02 [2]. Version numbering seems to follow a consistent yy.## format since 2015. [1] https://sourceforge.net/projects/sevenzip/files/7-Zip/ https://sourceforge.net/projects/sevenzip/files/7-Zip/ [2] https://sourceforge.net/p/sevenzip/discussion/45797/thread/9dbfea1e30/ https://sourceforge.net/p/sevenzip/discussion/45797/thread/9...

themitigating 4y ago

The versioning 7-zip only rule is to increase the value, there is no system

fomine3 4y ago
YY.increment? Looks reasonable versioning scheme for application.
- pvillano 4y ago
  esp w/ jetbrains and their yearly (?) releases that appear to add whatever features they finished since the last release. I've also seen yyyy.increment.build
- themitigating 4y ago
  It went from 4.65 to 9.04. Then later it jumped from 9.38 to 15.05. Then 16.02,16.03,16.04 , 17.00, 17.01, 18.00 These jumps don't correlate with major changes and major versions

emn13 4y ago

I'm not sure there's a "they" here; IIRC this is and always has been one man project by Igor Pavlov, who incidentally didn't just write the software, but also created the LZMA algorithm which has had an absurdly long run as one of the world-leading general purpose compression algorithms.

SECProto 4y ago

Looking back at this version history [1], there was perviously a gap of 3.5 years between releases (2011-2014). Skimming through the discussion forums, the 2.5yr gap between 19.00 and 21.07 was filled with a number of alpha and beta releases, eg 20.02 [2]. Version numbering seems to follow a consistent yy.## format since 2015. [1] https://sourceforge.net/projects/sevenzip/files/7-Zip/ https://sourceforge.net/projects/sevenzip/files/7-Zip/ [2] https://sourceforge.net/p/sevenzip/discussion/45797/thread/9dbfea1e30/ https://sourceforge.net/p/sevenzip/discussion/45797/thread/9...