Source Code Distribution Alongside Binary Distribution

It would be very nice to provide a source code distribution alongside
the binary distribution. In other words, package the source code from
which a binary release is being built and make it available for download.

At present it seems only the bleeding edge of the source code is
available from the CVS repository, which most likely is buggy,
incomplete or incompatible with previous versions. This is not helpful
if I have a problem with an older version. Simply creating a tag in CVS
whenever a stable build is released would help already, but I didn't
find that happening either.

This makes OPS undesirable for production, as there is no way to
correlate source code with the binary and prevents identifying the
origin of problems if they arise.

Sincerely,

Dirk Schalle



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Dirk,

 > It would be very nice to provide a source code distribution
 > alongside the binary distribution. In other words, package the
 > source code from which a binary release is being built and make it
 > available for download.

Yes, that would be a good thing to do.

 > At present it seems only the bleeding edge of the source code is
 > available from the CVS repository, which most likely is buggy,
 > incomplete

Mmhh... Let's say "unstable"? ;-)

 > or incompatible with previous versions. This is not helpful if I
 > have a problem with an older version. Simply creating a tag in CVS
 > whenever a stable build is released would help already, but I didn't
 > find that happening either.

Our automatic build system (which runs every hour and builds if a
checkin has occurred since the last build) tags all builds based on
the build version number. For stable builds, you can derive the tag
name from the file name. For example, you can update to OPS 3.5 M1
(ops-3.5.M1.200608310259.zip) using:

   cvs up -r TAG_OPS_3_5_M1_200608310259

For nightly builds, you can find the tag number in the build log:

   http://forge.objectweb.org/nightlybuilds/ops/ops/build.log

I still agree that bundling the sources in the release would be good.

 > This makes OPS undesirable for production, as there is no way to
 > correlate source code with the binary and prevents identifying the
 > origin of problems if they arise.

I hope the above helps a bit already,

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws