Hi Fernando, Unfortunately, I don't think we can do what you are asking without cutting a release. We don't publish snapshots of Jakarta Commons components. To cut a release, we need a release manager to volunteer, develop a plan, initiate a vote and then cut the release.
Any [discovery] volunteers? Phil On 4/15/05, Fernando Nasser <[EMAIL PROTECTED]> wrote: > Hi, > > I participate in some Open Source communities that distribute and use > Discovery. > > At JPackage we have an RPM with the 0.2 built from > http://www.apache.org/dist/jakarta/commons/discovery/source/commons-discovery-0.2-src.tar.gz > (everything is built from source so we can provide the source with the > binary as Open Source should). > > It happens that in the ObjectWeb JOnAS community they needed to use > instead an snapshot of 27-Mar-2004 due to some bugs in 0.2. > > If I update the JPackage RPM to an untagged version of the sources > people may complain and I am also afraid of some backward > incompatibility with that would affect the projects that currently use > the 0.2 Discovery. > > Would you consider tagging a 0.2.1 and making the source tar ball > available? Would that be backwards compatible? > > Thanks in advance for your attention. > > Regards to all, > Fernando > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
