On 02/17/2012 05:44 PM, Ryan Lubke wrote:
> As a follow up to this release, I'd like to discuss some items
> pertaining to Grizzly 2.x.
>
> We currently have been maintaining two different branches for grizzly
> 2.x development:
>
> - 2.1.x (2.1 development)
> - master (2.2 development)
>
> We have several issues on the tracker targeted for 2.3/3.0 (which will
> break compatibility
> with previous releases), so we'll probably snapshot the current master
> into a 2.2.x branch
> and allow the master to evolve for future releases.
>
> We've been doing our best to keep 2.1.x and master in sync with
> regards to fixes (git cherry-pick is great!), but
> I think trying to maintain this for three branches will be more work
> than we need right now.
>
> So I'd like to propose that after the 2.1.9 release, we won't do any
> more 2.1.x work except for really high priority issues (security, as
> an example).
>
> We'll limit the fix syncing to 2.2.x and master.
>
> Thoughts? Comments?
+1
WBR,
Alexey.
>
> Thanks,
> -rl
>
>
> On 2/17/12 8:31 AM, Oleksiy Stashok wrote:
>> Hey Folks,
>>
>> The Grizzly Team is happy to announce the release of Grizzly 2.1.9!
>>
>> The artifacts are available on maven central.
>>
>> Grizzly issues resolved: [1]
>>
>> Thanks to everyone who provided feedback and/or patches for this release!
>>
>> As usual, if there are additional suggestions on how to improve
>> Grizzly going forward,
>> or if a problem is discovered, please let us know by either logging
>> an issue [2] or
>> joining the mailing lists [3] and starting a discussion with the
>> community.
>>
>> Thanks!
>> - The Grizzly Team
>>
>> [1]
>> http://java.net/jira/secure/ReleaseNote.jspa?projectId=10005&version=15408
>> [2] http://java.net/jira/browse/GRIZZLY
>> [3] http://java.net/projects/grizzly/lists
>>
>>
>> Release Notes - grizzly - Version 2.1.9
>>
>> ** Bug
>> * [GRIZZLY-1014] - Content-type for files cached in the file
>> cache is incorrect
>> * [GRIZZLY-1069] - Response.reset() should offer similar
>> functionality as 1.9
>> * [GRIZZLY-1158] - UnsupportedOperationException:
>> org.glassfish.grizzly.threadpool.SyncThreadPool.awaitTermination
>> * [GRIZZLY-1173] - sync thread pool is getting overflowed
>> * [GRIZZLY-1174] - WS API needs the ability to send ping and pong
>> frames
>> * [GRIZZLY-1177] - MemoryManager, AttributeBuilder, and
>> SelectionKeyHandler provide default values with the intention of
>> allowing the default values to be changed.
>> * [GRIZZLY-1180] - Websocket upgrade request that is not accepted
>> by an application is dropped
>> * [GRIZZLY-1190] - WorkerThreadPool created when building
>> transport using SameThreadIOStrategy.
>> * [GRIZZLY-1191] - Unable to perform parallel writes using
>> blocking mode
>> * [GRIZZLY-1194] - False-positive result of selector empty-spin
>> checker
>>
>>
>> ** Task
>> * [GRIZZLY-1150] - Bring 1.9/2.1/2.2 WS implementations inline
>> with RFC 6455
>> * [GRIZZLY-1171] - Implement Adapters (empty implementations) for
>> Probe interfaces.
>>
>>
>>
>