From 1f42712eceb9db7f4ff81cc7e615848fdf045102 Mon Sep 17 00:00:00 2001
From: Kevin Rushforth
Release project Source code
-This release of the Java 3D source code based on Java 3D
-1.3.1 is
-available for download from the CVS repository of this project.
+
The current, experimental fork of the of the Java 3D source
+code is an early access of version 1.3.2. It is
+available for download from the CVS repository of this project.
This source release differs from the 1.3.1 release in the following +
This source release differs from the the current 1.3.1 release in
+the following
ways:
com.sun.j3d.*
packages have been split out into
+their own project (j3d-core-utils).We will work with the community to address bugs identified in
Java 3D
-1.3.1 and the will release new versions of Java 3D 1.3.x as
+1.3.1, and will release new versions of Java 3D 1.3.x as
needed.
Bug fixes will be immediately available in the CVS source, or from the
weekly builds on this site. We will release official 1.3.x versions no
@@ -75,15 +80,21 @@ more often than twice a year.
Java 3D 1.4
We will form a JSR and work with the community to -design and implement the next release of Java 3D. We envision 1.4 -including features such a programmable shaders. Our current aim is to +
We will file a new JSR (or revive the existing JSR-189) under the Java
+Community Process (JCP) shortly, and form an Expert Group of community
+members to
+design and implement the next version of the Java 3D API. We
+envision 1.4
+including features such as programmable shaders. Our goal is to
minimize large scale changes to the system in order to deliver 1.4 as
-quickly as possible. This initial direction may be changed by the JSR.
+quickly as possible. This initial direction could be changed by the
+Expert Group.
Java 3D 1.5/2.0
The scope of this release will be driven by the JSR. Our initial +
The scope of this release will be driven by the JSR Expert Group.
+Our initial
thoughts are that this work will include large scale changes to support
features such as extensibility and pluggable renderers.
[TODO: kcr: rewrite (and run spell check)]
-Anyone who wants to contribute source code, even e-mailed bug fixes, -must have a signed contributor agreement on file. The Java 3D -team is unable to even look at submitted bug fixes unless this author +
Anyone who wants to contribute source code, even in the form of
+e-mailed bug fixes,
+must have a signed contributor agreement [TODO link] on file. The
+Java 3D
+team regrets that we are unable to even look at submitted bug fixes
+unless this author
has the
contributor agreement on file. This may seems harsh, but it is a policy
-designed to protect the project from patent infringement, etc.
-
We encourage all developers to download the agreement, sign it, and
+designed to protect the project from patent infringement and copyright
+issues. We encourage all developers to download the agreement [TODO
+link], sign it, and
fax it
to the number indicated [TODO link]. Then you are more than welcome to
send in fixes for your favorite bugs!
As the community matures and contributors demonstrate their +
We invite anyone to be a project observer.
+As the community matures and contributors demonstrate their
familiarity
with the API internals they will be invited to join the project as a
-developer with full CVS commit privilege. The last thing we want is
+developer with full CVS commit
+privilege. The last thing we want is
lots of people hacking on the source in the central repository and
-destabilizing the API so we will be taking a cautious approach. We are
-not intending that Sun is the only organization with the rights to
-grant developer privilege, we would like to form a governance board
-with community members which will assume this mantel and help guide the
-project.
+destabilizing the API, so we will be taking a cautious approach.
The JCP process also has a significant impact on how people can +
The Java Community Process (JCP) also
+has a significant impact on how people can
contribute to the project. Although the source of the API is available,
and we actively encourage the community to contribute to it's
-development, the API itself (javax.media.j3d.* and javax.vecmath.*) are
-controlled by the JCP process and can not be freely modified.
+development, the API itself (that is, the public and protected classes,
+interfaces, methods, fields, and so forth in the javax.media.j3d
+and javax.vecmath
packages) are
+controlled by the JCP and can not be freely modified.
Modifications to the API will be created within the Java 3D JSR's
-by a
-group of JSR members. A call for nominations for JSR members will be
-made once this process is kicked off.
+by an Expert Group of JCP members. A call for experts will be
+made once this process is launched.
[TODO: links to code]
[TODO: links to examples]
+The j3d-examples
+project includes a set of simple example programs.
+
[TODO: links to other examples, e.g., j3dfly]
[TODO: list of feedback and participation options including mailing lists, -- cgit v1.2.3