Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #30805
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: JDK 1.7.0_75 and 1..8.0_31 are out |
| Date | 2015-01-22 21:23 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <m9rpoj$9m0$1@dont-email.me> (permalink) |
| References | (1 earlier) <8cvtba1g6nkgkcmtv0lbdqj2vmqldbqgk6@4ax.com> <bqvtbalicl6knu89d5togrh9fabe8gna3e@4ax.com> <54c05ce3$0$287$14726298@news.sunsite.dk> <qos0catvji0mr8r878cb6b238h9ccimlnp@4ax.com> <m9rceb$mci$1@dont-email.me> |
On Thu, 22 Jan 2015 11:36:37 -0600, Joshua Cranmer đ§ wrote: > <http://semver.org/> is the emerging standard for versioning. In short: > X.y.z-w An increase in X indicates a backwards-incompatible change. Code > that compiles with, e.g., 1.4.0 will not necessarily compile with 2.4.0 > An increase in Y indicates a major, but backwards-compatible change. > Code that compiles with 1.4.0 will compile with 2.0.0, but not > necessarily vice versa. > An increase in Z is a "bugfix" update: code that compiles with 1.4.1 > will work with 1.4.0. > The w qualifier is extra gunk that may be needed for build processes or > prerelease. > > As Java is unlikely to ever break backwards compatibility, that first > digit is probably going to stay 1 forever. > That is a useful reference. Thanks for posting it. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-20 17:10 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-20 17:16 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-20 17:24 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-01-21 21:13 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-21 19:53 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Joshua Cranmer đ§ <Pidgeot18@verizon.invalid> - 2015-01-22 11:36 -0600
Re: JDK 1.7.0_75 and 1..8.0_31 are out Martin Gregorie <martin@address-in-sig.invalid> - 2015-01-22 21:23 +0000
Re: JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-26 21:23 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Martin Gregorie <martin@address-in-sig.invalid> - 2015-01-27 11:00 +0000
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-01-24 21:27 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-01-24 22:07 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-01-24 22:21 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-26 21:29 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Joerg Meier <joergmmeier@arcor.de> - 2015-01-27 08:58 +0100
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-02-01 09:43 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2015-01-25 11:39 +0200
Re: JDK 1.7.0_75 and 1..8.0_31 are out Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2015-01-25 20:56 +0200
Re: JDK 1.7.0_75 and 1..8.0_31 are out Roedy Green <see_website@mindprod.com.invalid> - 2015-01-26 21:25 -0800
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-02-01 09:35 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-01-21 21:16 -0500
Re: JDK 1.7.0_75 and 1..8.0_31 are out Arne VajhĂžj <arne@vajhoej.dk> - 2015-01-21 21:22 -0500
csiph-web