On 02/08/2011 01:40, Christopher Schultz wrote:
> On 8/1/2011 2:58 PM, Mark Thomas wrote:
>> On 01/08/2011 19:32, Christopher Schultz wrote:
>>> On 8/1/2011 12:05 PM, Mark Thomas wrote:
On 01/08/2011 16:45, Christopher Schultz wrote:
> On 7/26/2011 1:30 PM, Mark Thomas wrote:
>> The Se
Mark,
On 8/1/2011 2:58 PM, Mark Thomas wrote:
> On 01/08/2011 19:32, Christopher Schultz wrote:
>> Mark,
>>
>> On 8/1/2011 12:05 PM, Mark Thomas wrote:
>>> On 01/08/2011 16:45, Christopher Schultz wrote:
Mark,
On 7/26/2011 1:30 PM, Mark Thomas wrote:
> The Servlet EG is starting
On 01/08/2011 19:32, Christopher Schultz wrote:
> Mark,
>
> On 8/1/2011 12:05 PM, Mark Thomas wrote:
>> On 01/08/2011 16:45, Christopher Schultz wrote:
>>> Mark,
>>>
>>> On 7/26/2011 1:30 PM, Mark Thomas wrote:
The Servlet EG is starting to discuss changes to the Servlet
API for 3.1. It
Mark,
On 8/1/2011 12:05 PM, Mark Thomas wrote:
> On 01/08/2011 16:45, Christopher Schultz wrote:
>> Mark,
>>
>> On 7/26/2011 1:30 PM, Mark Thomas wrote:
>>> The Servlet EG is starting to discuss changes to the Servlet API
>>> for 3.1. It would be useful if the option existed to implement some
>>>
On 01/08/2011 16:45, Christopher Schultz wrote:
> Mark,
>
> On 7/26/2011 1:30 PM, Mark Thomas wrote:
>> The Servlet EG is starting to discuss changes to the Servlet API
>> for 3.1. It would be useful if the option existed to implement some
>> of these changes in Tomcat trunk. The benefits of this
Mark,
On 7/26/2011 1:30 PM, Mark Thomas wrote:
> The Servlet EG is starting to discuss changes to the Servlet API for
> 3.1. It would be useful if the option existed to implement some of these
> changes in Tomcat trunk. The benefits of this are:
> - we can see how feasible the API changes are to i
On 26/07/2011 18:30, Mark Thomas wrote:
> The Servlet EG is starting to discuss changes to the Servlet API for
> 3.1. It would be useful if the option existed to implement some of these
> changes in Tomcat trunk. The benefits of this are:
> - we can see how feasible the API changes are to implement
On 07/27/2011 06:53 PM, Mark Thomas wrote:
On 27/07/2011 16:48, Mladen Turk wrote:
On 07/26/2011 07:30 PM, Mark Thomas wrote:
1. Should tomcat/tc7.0.x/trunk be RTC or CTR?
CTR
2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to
see earlier and more frequent alpha/beta r
On 27/07/2011 18:26, Mladen Turk wrote:
> On 07/27/2011 06:53 PM, Mark Thomas wrote:
>> On 27/07/2011 16:48, Mladen Turk wrote:
>>>
>>> After we release first 8 stable or starting from now?
>>
>> I was thinking announce EOL for 5.5.x now, with the actual EOL date /
>> last release ~August 2012.
>>
On 07/27/2011 06:53 PM, Mark Thomas wrote:
On 27/07/2011 16:48, Mladen Turk wrote:
After we release first 8 stable or starting from now?
I was thinking announce EOL for 5.5.x now, with the actual EOL date /
last release ~August 2012.
OK, but IMHO we should add +12 months to that for critic
On 27/07/2011 16:48, Mladen Turk wrote:
> On 07/26/2011 07:30 PM, Mark Thomas wrote:
>>
>> 1. Should tomcat/tc7.0.x/trunk be RTC or CTR?
>>
>
> CTR
>
>
>> 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to
>> see earlier and more frequent alpha/beta releases than we had for To
On 07/26/2011 07:30 PM, Mark Thomas wrote:
1. Should tomcat/tc7.0.x/trunk be RTC or CTR?
CTR
2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to
see earlier and more frequent alpha/beta releases than we had for Tomcat
Sure. This time we might have 8 ready as 3.1 spec is
2011/7/27 Mark Thomas :
> The Servlet EG is starting to discuss changes to the Servlet API for
> 3.1. It would be useful if the option existed to implement some of these
> changes in Tomcat trunk. The benefits of this are:
> - we can see how feasible the API changes are to implement
> - users can t
Meta: +1 to starting this thread and its thinking this early.
On Tue, Jul 26, 2011 at 1:30 PM, Mark Thomas wrote:
> Therefore, after the next Tomcat 7 release, I would like to do the
> following:
> - Copy tomcat/trunk to tomcat/tc7.0.x/trunk
> - Start making Servlet API changes to tomcat/trunk
+
+1 To getting newer ideas in faster.
I guess the question to ponder is what are the future changes pending for 7?
What are the changes for the servlet spec?
I have a feeling that the servlet spec changes are more of a playground for
ideas which would bring about lots of change and potential rever
On 27/07/2011 00:42, Konstantin Kolinko wrote:
> 2011/7/26 Mark Thomas :
>> The Servlet EG is starting to discuss changes to the Servlet API for
>> 3.1. It would be useful if the option existed to implement some of these
>> changes in Tomcat trunk. The benefits of this are:
>> - we can see how feas
On 07/26/2011 07:30 PM, Mark Thomas wrote:
The Servlet EG is starting to discuss changes to the Servlet API for
3.1. It would be useful if the option existed to implement some of these
changes in Tomcat trunk. The benefits of this are:
- we can see how feasible the API changes are to implement
-
2011/7/26 Mark Thomas :
> The Servlet EG is starting to discuss changes to the Servlet API for
> 3.1. It would be useful if the option existed to implement some of these
> changes in Tomcat trunk. The benefits of this are:
> - we can see how feasible the API changes are to implement
> - users can t
On 26.07.2011 19:30, Mark Thomas wrote:
> The Servlet EG is starting to discuss changes to the Servlet API for
> 3.1. It would be useful if the option existed to implement some of these
> changes in Tomcat trunk. The benefits of this are:
> - we can see how feasible the API changes are to implement
The Servlet EG is starting to discuss changes to the Servlet API for
3.1. It would be useful if the option existed to implement some of these
changes in Tomcat trunk. The benefits of this are:
- we can see how feasible the API changes are to implement
- users can try out the new APIs (assuming we d
20 matches
Mail list logo
