[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] jetty 7.4.0 ?
|
imo, we ought to just stick with the 7.3.1 as is and document that api
change on a new wiki page tracking such things from release to
release..
it is not one of the primary user classes being changed so not a minor
revision worthy change...we don't package anything in 'internal'
packages so imo we should play these api changes looser and what is
right for us as opposed to anything else
cheers,
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Wed, Mar 2, 2011 at 01:10, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
> Jesse (et al),
>
> I wanted to do a 7.3.1 this week, but the changes I put in for
> websocket draft 6 have changed a few APIs. Specifically the
> Connection interface, to which I have added one method and I've
> created an AbstractConnection class to hold some commons stuff between
> all the connection types.
>
> So strictly speaking, the next release should be a 7.4. because of the
> API changes. How long would it take to setup the needed release
> reviews for this?
>
> I could probably back out the changes and put a little fiddle in for
> the websocket stuff to keep the APIs the same and do a 7.3.1. I'm
> assuming that is what will be needed and am progressing on that basis.
>
> cheers
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
