|
Hi,
I can build 1.5.6 tomorrow. Is there a ticket that you prefer to be fixed for 1.5.6 ? Martin |
|
WICKET-4286 needs to be fixed. havent had time lately :/
-igor On Wed, Apr 25, 2012 at 7:33 AM, Martin Grigorov <[hidden email]> wrote: > Hi, > > I can build 1.5.6 tomorrow. > Is there a ticket that you prefer to be fixed for 1.5.6 ? > > Martin |
|
It is opened half an year ago. IMO It can wait for 1.5.7 but I don't
mind postponing 1.5.6 On Wed, Apr 25, 2012 at 6:32 PM, Igor Vaynberg <[hidden email]> wrote: > WICKET-4286 needs to be fixed. havent had time lately :/ > > -igor > > On Wed, Apr 25, 2012 at 7:33 AM, Martin Grigorov <[hidden email]> wrote: >> Hi, >> >> I can build 1.5.6 tomorrow. >> Is there a ticket that you prefer to be fixed for 1.5.6 ? >> >> Martin -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com |
|
we thought it was invalid until after 1.5.5 was released...someone
just recently provided a good usecase for it. but yeah, it is minor enough to wait. -igor On Wed, Apr 25, 2012 at 8:38 AM, Martin Grigorov <[hidden email]> wrote: > It is opened half an year ago. IMO It can wait for 1.5.7 but I don't > mind postponing 1.5.6 > > On Wed, Apr 25, 2012 at 6:32 PM, Igor Vaynberg <[hidden email]> wrote: >> WICKET-4286 needs to be fixed. havent had time lately :/ >> >> -igor >> >> On Wed, Apr 25, 2012 at 7:33 AM, Martin Grigorov <[hidden email]> wrote: >>> Hi, >>> >>> I can build 1.5.6 tomorrow. >>> Is there a ticket that you prefer to be fixed for 1.5.6 ? >>> >>> Martin > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com |
|
you have your working day to fix it :-)
otherwise either send me an email to not start the release or the fix will go in 1.5.7 On Wed, Apr 25, 2012 at 6:42 PM, Igor Vaynberg <[hidden email]> wrote: > we thought it was invalid until after 1.5.5 was released...someone > just recently provided a good usecase for it. > > but yeah, it is minor enough to wait. > > -igor > > On Wed, Apr 25, 2012 at 8:38 AM, Martin Grigorov <[hidden email]> wrote: >> It is opened half an year ago. IMO It can wait for 1.5.7 but I don't >> mind postponing 1.5.6 >> >> On Wed, Apr 25, 2012 at 6:32 PM, Igor Vaynberg <[hidden email]> wrote: >>> WICKET-4286 needs to be fixed. havent had time lately :/ >>> >>> -igor >>> >>> On Wed, Apr 25, 2012 at 7:33 AM, Martin Grigorov <[hidden email]> wrote: >>>> Hi, >>>> >>>> I can build 1.5.6 tomorrow. >>>> Is there a ticket that you prefer to be fixed for 1.5.6 ? >>>> >>>> Martin >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com |
|
so what was the point of asking the original question...
-igor On Wed, Apr 25, 2012 at 8:46 AM, Martin Grigorov <[hidden email]> wrote: > you have your working day to fix it :-) > otherwise either send me an email to not start the release or the fix > will go in 1.5.7 > > On Wed, Apr 25, 2012 at 6:42 PM, Igor Vaynberg <[hidden email]> wrote: >> we thought it was invalid until after 1.5.5 was released...someone >> just recently provided a good usecase for it. >> >> but yeah, it is minor enough to wait. >> >> -igor >> >> On Wed, Apr 25, 2012 at 8:38 AM, Martin Grigorov <[hidden email]> wrote: >>> It is opened half an year ago. IMO It can wait for 1.5.7 but I don't >>> mind postponing 1.5.6 >>> >>> On Wed, Apr 25, 2012 at 6:32 PM, Igor Vaynberg <[hidden email]> wrote: >>>> WICKET-4286 needs to be fixed. havent had time lately :/ >>>> >>>> -igor >>>> >>>> On Wed, Apr 25, 2012 at 7:33 AM, Martin Grigorov <[hidden email]> wrote: >>>>> Hi, >>>>> >>>>> I can build 1.5.6 tomorrow. >>>>> Is there a ticket that you prefer to be fixed for 1.5.6 ? >>>>> >>>>> Martin >>> >>> >>> >>> -- >>> Martin Grigorov >>> jWeekend >>> Training, Consulting, Development >>> http://jWeekend.com > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com |
|
you just said "but yeah, it is minor enough to wait.", no ?
so do you want me to wait you to fix it, to try to fix it myself or to build 1.5.6 ? On Wed, Apr 25, 2012 at 7:07 PM, Igor Vaynberg <[hidden email]> wrote: > so what was the point of asking the original question... > > -igor > > On Wed, Apr 25, 2012 at 8:46 AM, Martin Grigorov <[hidden email]> wrote: >> you have your working day to fix it :-) >> otherwise either send me an email to not start the release or the fix >> will go in 1.5.7 >> >> On Wed, Apr 25, 2012 at 6:42 PM, Igor Vaynberg <[hidden email]> wrote: >>> we thought it was invalid until after 1.5.5 was released...someone >>> just recently provided a good usecase for it. >>> >>> but yeah, it is minor enough to wait. >>> >>> -igor >>> >>> On Wed, Apr 25, 2012 at 8:38 AM, Martin Grigorov <[hidden email]> wrote: >>>> It is opened half an year ago. IMO It can wait for 1.5.7 but I don't >>>> mind postponing 1.5.6 >>>> >>>> On Wed, Apr 25, 2012 at 6:32 PM, Igor Vaynberg <[hidden email]> wrote: >>>>> WICKET-4286 needs to be fixed. havent had time lately :/ >>>>> >>>>> -igor >>>>> >>>>> On Wed, Apr 25, 2012 at 7:33 AM, Martin Grigorov <[hidden email]> wrote: >>>>>> Hi, >>>>>> >>>>>> I can build 1.5.6 tomorrow. >>>>>> Is there a ticket that you prefer to be fixed for 1.5.6 ? >>>>>> >>>>>> Martin >>>> >>>> >>>> >>>> -- >>>> Martin Grigorov >>>> jWeekend >>>> Training, Consulting, Development >>>> http://jWeekend.com >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com |
|
I was hoping it was going to be fixed in 1.5.6. We are releasing a
version of our product that while be heavily affected by this issue :(. -Nelson |
|
Ok then I won't build it tomorrow
Nelson Segura <[hidden email]> wrote: I was hoping it was going to be fixed in 1.5.6. We are releasing a version of our product that while be heavily affected by this issue :(. -Nelson |
|
the fix is trivial, at least on the surface. running tests now....
-igor On Wed, Apr 25, 2012 at 1:39 PM, Martin Grigorov <[hidden email]> wrote: > Ok then I won't build it tomorrow > > Nelson Segura <[hidden email]> wrote: > > I was hoping it was going to be fixed in 1.5.6. We are releasing a > version of our product that while be heavily affected by this issue > :(. > -Nelson > |
|
fixes pushed.
-igor On Wed, Apr 25, 2012 at 1:48 PM, Igor Vaynberg <[hidden email]> wrote: > the fix is trivial, at least on the surface. running tests now.... > > -igor > > On Wed, Apr 25, 2012 at 1:39 PM, Martin Grigorov > <[hidden email]> wrote: >> Ok then I won't build it tomorrow >> >> Nelson Segura <[hidden email]> wrote: >> >> I was hoping it was going to be fixed in 1.5.6. We are releasing a >> version of our product that while be heavily affected by this issue >> :(. >> -Nelson >> |
|
Is it available in SNAPSHOT? can I update and test?
-Nelson On Wed, Apr 25, 2012 at 2:16 PM, Igor Vaynberg <[hidden email]> wrote: > fixes pushed. > > -igor > > > On Wed, Apr 25, 2012 at 1:48 PM, Igor Vaynberg <[hidden email]> wrote: >> the fix is trivial, at least on the surface. running tests now.... >> >> -igor >> >> On Wed, Apr 25, 2012 at 1:39 PM, Martin Grigorov >> <[hidden email]> wrote: >>> Ok then I won't build it tomorrow >>> >>> Nelson Segura <[hidden email]> wrote: >>> >>> I was hoping it was going to be fixed in 1.5.6. We are releasing a >>> version of our product that while be heavily affected by this issue >>> :(. >>> -Nelson >>> |
|
http://ci.apache.org/builders/wicket-branch-1.5.x/builds/180
-igor On Wed, Apr 25, 2012 at 2:18 PM, Nelson Segura <[hidden email]> wrote: > Is it available in SNAPSHOT? can I update and test? > -Nelson > > On Wed, Apr 25, 2012 at 2:16 PM, Igor Vaynberg <[hidden email]> wrote: >> fixes pushed. >> >> -igor >> >> >> On Wed, Apr 25, 2012 at 1:48 PM, Igor Vaynberg <[hidden email]> wrote: >>> the fix is trivial, at least on the surface. running tests now.... >>> >>> -igor >>> >>> On Wed, Apr 25, 2012 at 1:39 PM, Martin Grigorov >>> <[hidden email]> wrote: >>>> Ok then I won't build it tomorrow >>>> >>>> Nelson Segura <[hidden email]> wrote: >>>> >>>> I was hoping it was going to be fixed in 1.5.6. We are releasing a >>>> version of our product that while be heavily affected by this issue >>>> :(. >>>> -Nelson >>>> |
|
1.5-SNAPSHOT is not very stable at the moment.
I reverted WICKET-4441 and filed WICKET-4518. Please test your apps against 1.5-SNAPSHOT if you can and report any issues to save us few days voting and rebuilding. On Thu, Apr 26, 2012 at 12:24 AM, Igor Vaynberg <[hidden email]> wrote: > http://ci.apache.org/builders/wicket-branch-1.5.x/builds/180 > > -igor > > On Wed, Apr 25, 2012 at 2:18 PM, Nelson Segura <[hidden email]> wrote: >> Is it available in SNAPSHOT? can I update and test? >> -Nelson >> >> On Wed, Apr 25, 2012 at 2:16 PM, Igor Vaynberg <[hidden email]> wrote: >>> fixes pushed. >>> >>> -igor >>> >>> >>> On Wed, Apr 25, 2012 at 1:48 PM, Igor Vaynberg <[hidden email]> wrote: >>>> the fix is trivial, at least on the surface. running tests now.... >>>> >>>> -igor >>>> >>>> On Wed, Apr 25, 2012 at 1:39 PM, Martin Grigorov >>>> <[hidden email]> wrote: >>>>> Ok then I won't build it tomorrow >>>>> >>>>> Nelson Segura <[hidden email]> wrote: >>>>> >>>>> I was hoping it was going to be fixed in 1.5.6. We are releasing a >>>>> version of our product that while be heavily affected by this issue >>>>> :(. >>>>> -Nelson >>>>> -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com |
| Powered by Nabble | Edit this page |
