dev@jsr311.java.net

RE: Design issues list

From: Jerome Louvel <jerome.louvel_at_noelios.com>
Date: Sat, 19 May 2007 16:03:04 +0200

Hi Marc,

Using the issue list sounds good for the additional tracking support. Maybe
using the Wiki still makes sense for the design synthesis work and broader
topics that don't fit into the issue concept?

Best regards,
Jerome

> -----Message d'origine-----
> De : Marc.Hadley_at_Sun.COM [mailto:Marc.Hadley_at_Sun.COM]
> Envoyé : vendredi 18 mai 2007 16:56
> À : dev_at_jsr311.dev.java.net
> Objet : Re: Design issues list
>
> I suggest we use the issue tracker:
>
> https://jsr311.dev.java.net/servlets/ProjectIssues
>
> So far we've had a pretty wide ranging discussion that has focussed
> on the general approach more than specific issues. As we progress I
> expect to transition to a more issue-driven approach and perhaps now
> would be a good time to see if we're ready to do that.
>
> I've added a first issue for the question of whether to expand @
> [Produce|Consume][MediaType|Mime] to cover additional metadata for
> content negotiation or not:
>
> https://jsr311.dev.java.net/issues/show_bug.cgi?id=1
>
> Marc.
>
> On May 18, 2007, at 9:57 AM, Jerome Louvel wrote:
>
> >
> > Hi all,
> >
> > This question is more directed towards Paul and Marc: is
> there some
> > kind of
> > design issues list or similar tracking information available for
> > this JSR?
> >
> > In any case, I think it would be helpful to have a public and
> > collective way
> > to share such information. I suggest using Wiki pages on the JSR's
> > java.net
> > project. This would help us consolidate our views and build a
> > consensus.
> >
> > Best regards,
> > Jerome Louvel
> > --
> > http://www.restlet.org
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> > For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
> >
>
> ---
> Marc Hadley <marc.hadley at sun.com>
> CTO Office, Sun Microsystems.
>
>
>