webrev accessibility

Frederic Simon freds at jfrog.org
Tue Nov 6 19:03:07 UTC 2007


In a lot of Java open source software (JBoss, Codehaus, some Apache
projects), they use JIRA and the integration with VCS (Subversion, CVS, ...)
to manage the flow and validation of a task.
A task with all the code patches associated looks like:
http://www.jfrog.org/jira/browse/RTFACT-258?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel

All patches/comments/validation are linked here in the task. The patch code
in jfrog is visible with viewvc for Subversion. But Mercurial gitweb
look&feel for OpenJDK is better and looks like:
http://www.jfrog.org/hg/openJDK/MASTER/langtools/rev/f5877e328128

My 2cts on this issue.
I really hope the interface will have an easy search and browse, beacuse
today's bug DB is quite annoying.

Good luck.

On 11/6/07, Mark Reinhold <mr at sun.com> wrote:
>
> > Date: Tue, 06 Nov 2007 13:22:44 -0500
> > From: paul.hohensee at sun.com
>
> > ...
> >
> > My question is, where can we store webrevs so they're accessible to
> > the community, and what's the process for putting them there?
>
> This was discussed a few weeks ago [1].  Those of us hacking on the
> infrastructure are focused on Mercurial at the moment, but we hope to
> get to the webrev problem soon.
>
> - Mark
>
>
> [1] http://thread.gmane.org/gmane.comp.java.openjdk.general/446
>



-- 
http://freddy33.bglogspot.com/
http://www.jfrog.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/build-dev/attachments/20071106/5733a1b8/attachment.html>


More information about the build-dev mailing list