wicket-8 m8

2017-09-25 Thread Korbinian Bachl 
Hi,

due to the problematic bugs in wicket8 up to m7 (2 x pagestore and 
filesystemresource-leak), would it be possible to release wicket8-m8 anytime 
soon?

Best,

Korbinian

Re: wicket-8 m8

2017-09-25 Thread Maxim Solodovnik 
WICKET-6105  seems to be
blocker for 8.0.0 release
Do we have any blockers for M8?

On Mon, Sep 25, 2017 at 2:24 PM, Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:

> Hi,
>
> due to the problematic bugs in wicket8 up to m7 (2 x pagestore and
> filesystemresource-leak), would it be possible to release wicket8-m8
> anytime soon?
>
> Best,
>
> Korbinian
>



-- 
WBR
Maxim aka solomax

Re: wicket-8 m8

2017-09-25 Thread Andrea Del Bene 
No AFAIK but I'd rather wait for WICKET-6105 to be solved. It's a delicate
issue and I would like to collect as many user feedback as possible before
publishing the final 8.0.0

On Mon, Sep 25, 2017 at 9:40 AM, Maxim Solodovnik 
wrote:

> WICKET-6105  seems to
> be
> blocker for 8.0.0 release
> Do we have any blockers for M8?
>
> On Mon, Sep 25, 2017 at 2:24 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
> > Hi,
> >
> > due to the problematic bugs in wicket8 up to m7 (2 x pagestore and
> > filesystemresource-leak), would it be possible to release wicket8-m8
> > anytime soon?
> >
> > Best,
> >
> > Korbinian
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: wicket-8 m8

2017-09-25 Thread Sebastien 
Maybe a -M8 in the meantime?

As well as 6.29 so releases cycle stay aligned? (btw, does the page store
issue not applies to wicket-6.x?)

On Mon, Sep 25, 2017 at 11:03 AM, Andrea Del Bene 
wrote:

> No AFAIK but I'd rather wait for WICKET-6105 to be solved. It's a delicate
> issue and I would like to collect as many user feedback as possible before
> publishing the final 8.0.0
>

Re: wicket-8 m8

2017-09-25 Thread Andrea Del Bene 



On 25/09/2017 11:58, Sebastien wrote:

Maybe a -M8 in the meantime?
I agree but the next milestone in my opinion should contain WICKET-6105. 
I would discourage to release WICKET-6105 directly into 8.0.0 without 
testing it in a milestone version. If this fix can be solved in the very 
next days I prefer waiting for it.


As well as 6.29 so releases cycle stay aligned? (btw, does the page store
issue not applies to wicket-6.x?)
Not sure about the page store issue, but I also agree that a 6.29.0 
should be released.


On Mon, Sep 25, 2017 at 11:03 AM, Andrea Del Bene 
wrote:


No AFAIK but I'd rather wait for WICKET-6105 to be solved. It's a delicate
issue and I would like to collect as many user feedback as possible before
publishing the final 8.0.0

Re: wicket-8 m8

2017-09-26 Thread Andrea Del Bene 
Wicket 6.x is affected by page store issue. I'm going to build a 6.29.0 
asap.



On 25/09/2017 14:31, Andrea Del Bene wrote:



On 25/09/2017 11:58, Sebastien wrote:

Maybe a -M8 in the meantime?
I agree but the next milestone in my opinion should contain 
WICKET-6105. I would discourage to release WICKET-6105 directly into 
8.0.0 without testing it in a milestone version. If this fix can be 
solved in the very next days I prefer waiting for it.


As well as 6.29 so releases cycle stay aligned? (btw, does the page 
store

issue not applies to wicket-6.x?)
Not sure about the page store issue, but I also agree that a 6.29.0 
should be released.


On Mon, Sep 25, 2017 at 11:03 AM, Andrea Del Bene 
wrote:

No AFAIK but I'd rather wait for WICKET-6105 to be solved. It's a 
delicate
issue and I would like to collect as many user feedback as possible 
before

publishing the final 8.0.0

Re: wicket-8 m8

2017-09-26 Thread Andrea Del Bene 

I've committed the page store fix for 6.x

https://github.com/apache/wicket/commit/8b9e82ffece4e94317b9efcaa5018d6076d86568


On 26/09/2017 13:58, Andrea Del Bene wrote:
Wicket 6.x is affected by page store issue. I'm going to build a 
6.29.0 asap.



On 25/09/2017 14:31, Andrea Del Bene wrote:



On 25/09/2017 11:58, Sebastien wrote:

Maybe a -M8 in the meantime?
I agree but the next milestone in my opinion should contain 
WICKET-6105. I would discourage to release WICKET-6105 directly into 
8.0.0 without testing it in a milestone version. If this fix can be 
solved in the very next days I prefer waiting for it.


As well as 6.29 so releases cycle stay aligned? (btw, does the page 
store

issue not applies to wicket-6.x?)
Not sure about the page store issue, but I also agree that a 6.29.0 
should be released.


On Mon, Sep 25, 2017 at 11:03 AM, Andrea Del Bene 


wrote:

No AFAIK but I'd rather wait for WICKET-6105 to be solved. It's a 
delicate
issue and I would like to collect as many user feedback as possible 
before

publishing the final 8.0.0