On Thu, Aug 28, 2008 at 2:59 PM, Paul Sandoz <Paul.Sandoz_at_sun.com> wrote:
> Imran M Yousuf wrote:
>>>
>>> I would be interested in hearing feedback on the rate of which we should
>>> evolve the Jersey APIs. We will need to make some package name changes
>>> and
>>> clean up the boundaries between modules. Part of the motivation for this
>>> is
>>> to make Jersey OSGi-enabled. Given our schedule this is likely to happen
>>> after 1.0.0.0 as a 1.0.x.y release, say 1.0.1.y, where 'x' signifies a
>>> change in the Jersey APIs and 'y' signifies a change in implementation
>>> (for
>>> Jersey to be a 1.1 release requires that there be a JAX-RS 1.1 version).
>>>
>>
>> To be honest this time around the "0.10" version was creating some
>> discomfort for me, it would be more confortable if version were like
>> "1.0.x.yy" with x and y signifying the same meaning as mentioned by
>> you.
>
> Unfortunately we cannot call things 1.0 yet. Every release corresponded to
> API changes (311 and Jersey) and we did not have the resources to do stable
> point releases while also implementing/tracking changes. So the best i could
> do was align the Jersey version with the API version and release regularly
> about every 6 weeks.
>
I understood that and thus mentioned "discomfort" :) otherwise would
have probably used something better to say that 'it was not necessary'
:).
>
>> I would like to see frequent stable 'yy' releases to make the
>> latest fixes and implementations improvements public instead of asking
>> to use SNAPSHOTS to avail them.
>>
>
> We have our maven release process such that it is nearly automated. I think
> Jakub has things set up so it may almost be possible to tag, convert, build
> and deploy in one or two steps.
>
> However, there are some additional factors to releasing. Every time we
> release we need to test, and this still takes time, so we need to automate
> tests for the examples (adding stuff to the test directory, this can also
> serve as examples of how to use the client API). So for the spring example i
> encourage you to use the unit test framework for the client interactions :-)
>
I will do that for sure. This weekend is a good time for it :). The
splendid automated processes makes it even simpler to test and make
frequent (say once a month if there is enough changes) doesn't it?
> In addition we need to set up a Hudson matrix job to run the jersey tests
> and examples on a number of platforms and JDK versions.
>
>
>> Also in this regard for samples, I would like to add "1.0.x.yy.zz" in
>> order to incorporate new and richer samples as they are integrated
>> into trunk.
>>
>
> If we release regularly and often i am not sure if this is really necessary
> i.e. for testing/experimental purposes the SNAPSHOT build can be used. My
> preference is to keep all Jersey related modules in sync and released at the
> same time rather than spinning some modules faster than others. It is easier
> to manage and there is a clear indication that all modules of the same
> version have been tested together. If some modules need to be spun at
> different rates then i think it implies that module should be a separate
> project.
>
I agree with both points mentioned, if we release often I would not
mind waiting for getting the latest samples neither would I mind if
the samples is a separate project as well. Speaking about samples, as
I mentioned in another thread, I am working on a sample of NetBeans
RCP + Jersey + Spring + Hibernate. So I would be interested to propose
that as a 'comprehensive' sample as well. Its current repository is -
http://repo.or.cz/w/smart-selection-suite.git?a=shortlog;h=refs/heads/rest-with-jersey
(pointing to the branch directly)
Cheers,
- Imran
> Paul.
>
> --
> | ? + ? = To question
> ----------------\
> Paul Sandoz
> x38109
> +33-4-76188109
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
--
Imran M Yousuf
Email: imran_at_smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557