>- Decide on the version number. > We had a very small/brief discussion about this during Fosdem. > Everybody seems to agree 0.x really doesn't do justice to the maturity > we have reached over the years. And it is really hard to define when > we hit "1.0". So the proposal is to keep using a "sequence version > number". Either just drop the "0." and make the next release-number > classpath-21, or adopt a year.month style version number and make the > next version number classpath-6.3 for the March 2006 release. > In either case we will just use a code name for a release that has > some special feature set that we are proud of, but we will always > just increase the release snapshot number. Suggestions or Opinions? I think the best wold be, if GNU Classpath 1.0 is 100% compatible to Java 1.4 and GNU Classpath 2.0 would be 100% compatible to Java 1.5. The reason: Dates are also nice version numbers. But they don't seem for me like "versions". The packages at http://builder.classpath.org/dist/ can be becomming names like classpath-06-03-01.tar.gz and so on (which would be nice, because at the moment all snapshots have the same name), but not releases. Calling a mostly 1.4 compatible GNU Classpath 1.4.x and a mostly 1.5 compatible GNU Classpath 1.5.x, is something I don't like. This means, that after 0.20 comes 1.4. That is a big step, which firms for commercial products do (somebody says to me, that there existing a commercial program, which begins with the version number 2.1), but not for an OpenSource-product. GNU Classpath is not compatible to Java. In the current version of GNU Classpath are classes, which are at first in Java 1.5 and there are other classes, which existing since Java 1.4, which are still not compatible to Suns Java. So, GNU Classpath isn't Suns Java. And it makes in my eyes no sense, to give it the same version numbers like Suns Java. If anybody want to know to which Java-version GNU Classpath is compatible, everybody can read the GNU Classpath release notes or look at the proberty "java.version". The most people who looks at GNU Classpath are knowing about it. They don't need a version number like Suns one. But a 1.0 if GNU Classpath seems to be really 100% compatible to Java 1.4 would be nice. But until this, there is still a long way. It's a pity, that there existing no JavaVM, which used GNU Classpath and want's to be J2SE 1.4 certified. So, the step to GNU Classpath 1.0 would be by looking, if all Java 1.4 programs which everybody know can be running with GNU Classpath. To give a Java 1.5 compatible GNU Classpath the version 2.0 is in my eyes justifiable, because with new features like generics, it needs new Compiler and new JVMs. And to find the time to give GNU Classpath the version 2.0 would be much easier. Because Apache Harmony wants to be J2SE 1.5 certified, GNU Classpath can be known 2.0 as soon as Harmony have its certification. Greatings theuserbl
