Hi, I was wondering if you have considered using JIRA as issue tracker instead of the suplied by google code. Many open source projects uses it (such as JBoss Errai, at https://issues.jboss.org/browse/ERRAI ) and I think it is far superior than the vanilla google code issue tracker - for the developers and for the community.
I was thinking about it because of the fact most of (all?) the issues fixed on 2.6.0 release are marked as "Fixed_Not_Released" - which implies you don't have an automatic script to update those issues on release... and I don't know if this kind of task could be scripted using google code APIs. The fact is you can do that using JIRA, beside all other advantages. Anyway, using JIRA, google code or any other issue tracker, I think you should automatize the process of releasing the package (including uploads of the binary, the source and the javadoc to gwtproject.org and to Maven central) and closing the related issues at the issue tracker, to avoid awkward situations with the project documentation. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
