On 05/01/2014 04:49 PM, Christopher Ainsley wrote:
> Hello,
> I'm one of the principle committers on JavaCC, and I wanted to ask the
> procedure to have the debian JavaCC package updated to the latest
> version of JavaCC, 6.1.0.
> JavaCC is now live here:
> https://java.net/projects/javacc/downloads/directory/releases/Release%206.1.0
> And is up on Maven Central ::
> http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22net.java.dev.javacc%22
> Let me know as to the procedure for updating the package or if you
> require any information from myself prior to being able to update the
> package.
> Regards,
> Chris Ainsley

Hi Chris,

Thank you for the notification about the new upstream version.  The
typical procedure is to file a severity wishlist bug against the
existing source package requesting an update to a new upstream version.
 All bugs filed against Java Team packages will notify the team via email.

In the case of JavaCC, there was already a bug filed for the 6.0 release
last December [1].  I have retitled to refer to 6.x.

As far as getting the package actually updated, the Java Team is fairly
"lean" in terms of members relative to the number of packages and
ongoing efforts, so how quickly the bug is resolved can vary depending
on package popularity, developer interest, urgency (e.g., a security
defect), how many new build dependencies are required, etc.  If you're
keen on seeing the package updated quickly, you can work on an updated
package and request sponsorship (via the debian-java list), or you may
even opt to join the Java Team and commit directly to the pkg-java
packaging repo.

That said, I'll take a look at the new release and see what's involved
with getting a new version into Debian.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732752

Attachment: signature.asc
Description: OpenPGP digital signature

This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to