jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31870] New: - Unreproducible build: improve release tagging and source distribution
Date Sun, 24 Oct 2004 23:22:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31870>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31870

Unreproducible build: improve release tagging and source distribution

           Summary: Unreproducible build: improve release tagging and source
                    distribution
           Product: Taglibs
           Version: 1.1.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: String Taglib
        AssignedTo: taglibs-dev@jakarta.apache.org
        ReportedBy: jberry@apache.org


I'm reporting this bug for the string taglib, but I have a feeling the issue may be rampant
through 
taglibs other than standard, which seems to have done a better job.

There seem to be a number of problems with the source and release control for this project.

 (1) There are no source distributions available other than nightly builds. So the only way
to recreate a 
particular release, or even find the software it's based on, is to checkout from cvs. YOU
SHOULD 
CREATE A SOURCE DISTRO TO GO WITH YOUR BINARY DISTROS, AND POST IT. Standard does this 
appropriately.

 (2) Even within cvs, you don't seem to have properly tagged the release. For instance, I
see a tag 
string-1-1_POSTRELEASE, but no string-1-1. I have no idea whether this is a tag for the 1.1
release, or 
something that came afterwards ("post") the release. YOU SHOULD CLEARLY TAG EACH SOURCE 
RELEASE WITHIN CVS.

 (3) But when I jump off the cliff and grab that unknown release tagged string-1-1_POSTRELEASE,
it is 
not buildable. It relies on several files at the root above it (common.xml, etc) which were
not tagged 
with the release. So while I can grab something off head that may work, I don't know what
should have 
been used to build the release. ALL FILES NEEDED TO BUILD THE RELEASE SHOULD BE TAGGED/
RELEASED WITH THE RELEASE.

Sorry for the shouting. I'm frustrated in trying to build your code. Please cleanup your release
process.

-jdb

---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org


Mime
View raw message