You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martin Grigorov <mg...@apache.org> on 2012/06/25 22:17:42 UTC
[Vote] 6.0.0 -beta3 or RC1 ?
Hi,
It is almost one month since 6.0.0-beta2 and there are 43 resolved
issues. We have to decide whether the next will be beta3 or RC1.
In the last month there were some API changes related to the generics
in the SortState in wicket-extensions,
IResourceStreamWriter#write(Response) is reverted back to
#write(OutputStream) (contributed by Jesse Long) and form submitter's
#onSubmit() splitted to #onSubmitBeforeForm() and #onSubmitAfterForm()
(Carl-Eric).
The changes are not big but I want you to take them into account
before deciding whether it is time for RC1.
There is also a ticket about removing completely
IResourceStream#close() -
https://issues.apache.org/jira/browse/WICKET-4600.
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Martin Grigorov <mg...@apache.org>.
On Wed, Jun 27, 2012 at 10:12 AM, Martijn Dashorst
<ma...@gmail.com> wrote:
> On Wed, Jun 27, 2012 at 10:05 AM, Martin Grigorov <mg...@apache.org> wrote:
>> On Wed, Jun 27, 2012 at 12:06 AM, Martijn Dashorst
>> <ma...@gmail.com> wrote:
>>> We should just release 6.0. The RC's are the things we create for
>>> ourselves during the release process. There really is no need IMO to
>>> push a RC to the mirrors and Maven central for the 10 odd folks
>>> downloading those. A final release is something people actually care
>>> about.
>>
>> My experience with 1.5 is that the not many users used the milestones
>> but more started using the RCs and reported issues.
>> But it will be the same with a final release so I don't really need a RC.
>> The only difference is that now it wont be possible to do even minor
>> API breaks as we did in 1.5 RCs, for good or bad.
>
> My experience is that even in 1.5 not many folks were using the RCs.
> But an RC must not have any api breaks to begin with.
>
> If we uncover a bad API (which I am certain exists in Wicket), we fix
> in Wicket 7 (I hope we are still go for wicket 7? :-). At least from
> my perspective, we are able to build and run one of our 1000+ page
> applications using Wicket 6, so I don't think there are any gaping
> holes in our API. Minor issues, probably.
>
>> I can write something about Ajax and Native WebSockets at
>> http://wicketinaction.com.
>
> Great, I'm looking forward to those!
Now I'm thinking that maybe it will be better if someone else writes
an app and/or an article about the stuff I did for Wicket 6.
This way another mind will have to digest it and see what is good and
what is not that good.
I can do the same for the resource management (bundles, dependencies
and header items) done by Emond.
>
> Martijn
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Martijn Dashorst <ma...@gmail.com>.
On Wed, Jun 27, 2012 at 10:05 AM, Martin Grigorov <mg...@apache.org> wrote:
> On Wed, Jun 27, 2012 at 12:06 AM, Martijn Dashorst
> <ma...@gmail.com> wrote:
>> We should just release 6.0. The RC's are the things we create for
>> ourselves during the release process. There really is no need IMO to
>> push a RC to the mirrors and Maven central for the 10 odd folks
>> downloading those. A final release is something people actually care
>> about.
>
> My experience with 1.5 is that the not many users used the milestones
> but more started using the RCs and reported issues.
> But it will be the same with a final release so I don't really need a RC.
> The only difference is that now it wont be possible to do even minor
> API breaks as we did in 1.5 RCs, for good or bad.
My experience is that even in 1.5 not many folks were using the RCs.
But an RC must not have any api breaks to begin with.
If we uncover a bad API (which I am certain exists in Wicket), we fix
in Wicket 7 (I hope we are still go for wicket 7? :-). At least from
my perspective, we are able to build and run one of our 1000+ page
applications using Wicket 6, so I don't think there are any gaping
holes in our API. Minor issues, probably.
> I can write something about Ajax and Native WebSockets at
> http://wicketinaction.com.
Great, I'm looking forward to those!
Martijn
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Wed, Jun 27, 2012 at 12:06 AM, Martijn Dashorst
<ma...@gmail.com> wrote:
> We should just release 6.0. The RC's are the things we create for
> ourselves during the release process. There really is no need IMO to
> push a RC to the mirrors and Maven central for the 10 odd folks
> downloading those. A final release is something people actually care
> about.
My experience with 1.5 is that the not many users used the milestones
but more started using the RCs and reported issues.
But it will be the same with a final release so I don't really need a RC.
The only difference is that now it wont be possible to do even minor
API breaks as we did in 1.5 RCs, for good or bad.
>
> Considering that at my € work place some build is running Wicket 6
> snapshot, I don't think there are any major API issues lurking.
> Although I need to check something with the resources API that Emond
> crafted (utility methods that make the API better discoverable).
>
> As per ASF release policy we don't release binaries, but a source
> release, it is actually easier to do so: no automatic downloading of
> pre-releases by maven, borking your local build systems. Just run mvn
> install in the downloaded distribution and you're set. The source
> distributions and signatures can easily be renamed to 6.0 prior to
> uploading to the mirroring system. The only things that are impossible
> to change are the maven pom version numbers, as they crap up the
> signing bits.
>
> But before we do the release I want a new website design for 6.0. The
> current one is roughly 5 years old or so. It really needs a decent
> scrubbing. I'd like some articles for new 6.0 features. Often these
> articles uncover holes in our APIs: actually using and trying to
> describe some part triggers that. Rubber Duck debugging but then
> applied to API design :-)
I can write something about Ajax and Native WebSockets at
http://wicketinaction.com.
>
> Let me mull for a few days on a 6.0 release plan. If you have ideas,
> just send them to dev@ (subject "6.0 release plan"). Just to be clear,
> I intend to complete the 6.0 release in 2-3 weeks.
>
> Martijn
>
> On Mon, Jun 25, 2012 at 10:30 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>> +1 for RC1
>>
>> -igor
>>
>> On Mon, Jun 25, 2012 at 1:17 PM, Martin Grigorov <mg...@apache.org> wrote:
>>> Hi,
>>>
>>> It is almost one month since 6.0.0-beta2 and there are 43 resolved
>>> issues. We have to decide whether the next will be beta3 or RC1.
>>>
>>> In the last month there were some API changes related to the generics
>>> in the SortState in wicket-extensions,
>>> IResourceStreamWriter#write(Response) is reverted back to
>>> #write(OutputStream) (contributed by Jesse Long) and form submitter's
>>> #onSubmit() splitted to #onSubmitBeforeForm() and #onSubmitAfterForm()
>>> (Carl-Eric).
>>> The changes are not big but I want you to take them into account
>>> before deciding whether it is time for RC1.
>>>
>>> There is also a ticket about removing completely
>>> IResourceStream#close() -
>>> https://issues.apache.org/jira/browse/WICKET-4600.
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Martijn Dashorst <ma...@gmail.com>.
We should just release 6.0. The RC's are the things we create for
ourselves during the release process. There really is no need IMO to
push a RC to the mirrors and Maven central for the 10 odd folks
downloading those. A final release is something people actually care
about.
Considering that at my € work place some build is running Wicket 6
snapshot, I don't think there are any major API issues lurking.
Although I need to check something with the resources API that Emond
crafted (utility methods that make the API better discoverable).
As per ASF release policy we don't release binaries, but a source
release, it is actually easier to do so: no automatic downloading of
pre-releases by maven, borking your local build systems. Just run mvn
install in the downloaded distribution and you're set. The source
distributions and signatures can easily be renamed to 6.0 prior to
uploading to the mirroring system. The only things that are impossible
to change are the maven pom version numbers, as they crap up the
signing bits.
But before we do the release I want a new website design for 6.0. The
current one is roughly 5 years old or so. It really needs a decent
scrubbing. I'd like some articles for new 6.0 features. Often these
articles uncover holes in our APIs: actually using and trying to
describe some part triggers that. Rubber Duck debugging but then
applied to API design :-)
Let me mull for a few days on a 6.0 release plan. If you have ideas,
just send them to dev@ (subject "6.0 release plan"). Just to be clear,
I intend to complete the 6.0 release in 2-3 weeks.
Martijn
On Mon, Jun 25, 2012 at 10:30 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> +1 for RC1
>
> -igor
>
> On Mon, Jun 25, 2012 at 1:17 PM, Martin Grigorov <mg...@apache.org> wrote:
>> Hi,
>>
>> It is almost one month since 6.0.0-beta2 and there are 43 resolved
>> issues. We have to decide whether the next will be beta3 or RC1.
>>
>> In the last month there were some API changes related to the generics
>> in the SortState in wicket-extensions,
>> IResourceStreamWriter#write(Response) is reverted back to
>> #write(OutputStream) (contributed by Jesse Long) and form submitter's
>> #onSubmit() splitted to #onSubmitBeforeForm() and #onSubmitAfterForm()
>> (Carl-Eric).
>> The changes are not big but I want you to take them into account
>> before deciding whether it is time for RC1.
>>
>> There is also a ticket about removing completely
>> IResourceStream#close() -
>> https://issues.apache.org/jira/browse/WICKET-4600.
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Carl-Eric Menzel <cm...@wicketbuch.de>.
+1 for beta3 in a few days.
I'd like to get my cleanup of ResourceStreamLocator in before we freeze
the API. I'm not sure yet whether I'll have a breaking change (possibly
changing getResourceFinder() in Application to return a list rather
than just a single one).
Carl-Eric
On Mon, 25 Jun 2012 13:30:36 -0700
Igor Vaynberg <ig...@gmail.com> wrote:
> +1 for RC1
>
> -igor
>
> On Mon, Jun 25, 2012 at 1:17 PM, Martin Grigorov
> <mg...@apache.org> wrote:
> > Hi,
> >
> > It is almost one month since 6.0.0-beta2 and there are 43 resolved
> > issues. We have to decide whether the next will be beta3 or RC1.
> >
> > In the last month there were some API changes related to the
> > generics in the SortState in wicket-extensions,
> > IResourceStreamWriter#write(Response) is reverted back to
> > #write(OutputStream) (contributed by Jesse Long) and form
> > submitter's #onSubmit() splitted to #onSubmitBeforeForm() and
> > #onSubmitAfterForm() (Carl-Eric).
> > The changes are not big but I want you to take them into account
> > before deciding whether it is time for RC1.
> >
> > There is also a ticket about removing completely
> > IResourceStream#close() -
> > https://issues.apache.org/jira/browse/WICKET-4600.
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Martin Grigorov <mg...@apache.org>.
+1 for RC1
@Carl-Eric: we can postpone RC1 until you make this change
Also I like what Pedro suggested for WICKET-4575: onSubmit() + onAfterSubmit()
On Tue, Jun 26, 2012 at 12:58 AM, Carl-Eric Menzel
<cm...@wicketbuch.de> wrote:
> +1 for beta3 in a few days.
>
> I'd like to get my cleanup of ResourceStreamLocator in before we freeze
> the API. I'm not sure yet whether I'll have a breaking change (possibly
> changing getResourceFinder() in Application to return a list rather
> than just a single one).
>
> Carl-Eric
>
> On Mon, 25 Jun 2012 13:30:36 -0700
> Igor Vaynberg <ig...@gmail.com> wrote:
>
>> +1 for RC1
>>
>> -igor
>>
>> On Mon, Jun 25, 2012 at 1:17 PM, Martin Grigorov
>> <mg...@apache.org> wrote:
>> > Hi,
>> >
>> > It is almost one month since 6.0.0-beta2 and there are 43 resolved
>> > issues. We have to decide whether the next will be beta3 or RC1.
>> >
>> > In the last month there were some API changes related to the
>> > generics in the SortState in wicket-extensions,
>> > IResourceStreamWriter#write(Response) is reverted back to
>> > #write(OutputStream) (contributed by Jesse Long) and form
>> > submitter's #onSubmit() splitted to #onSubmitBeforeForm() and
>> > #onSubmitAfterForm() (Carl-Eric).
>> > The changes are not big but I want you to take them into account
>> > before deciding whether it is time for RC1.
>> >
>> > There is also a ticket about removing completely
>> > IResourceStream#close() -
>> > https://issues.apache.org/jira/browse/WICKET-4600.
>> >
>> > --
>> > Martin Grigorov
>> > jWeekend
>> > Training, Consulting, Development
>> > http://jWeekend.com
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [Vote] 6.0.0 -beta3 or RC1 ?
Posted by Igor Vaynberg <ig...@gmail.com>.
+1 for RC1
-igor
On Mon, Jun 25, 2012 at 1:17 PM, Martin Grigorov <mg...@apache.org> wrote:
> Hi,
>
> It is almost one month since 6.0.0-beta2 and there are 43 resolved
> issues. We have to decide whether the next will be beta3 or RC1.
>
> In the last month there were some API changes related to the generics
> in the SortState in wicket-extensions,
> IResourceStreamWriter#write(Response) is reverted back to
> #write(OutputStream) (contributed by Jesse Long) and form submitter's
> #onSubmit() splitted to #onSubmitBeforeForm() and #onSubmitAfterForm()
> (Carl-Eric).
> The changes are not big but I want you to take them into account
> before deciding whether it is time for RC1.
>
> There is also a ticket about removing completely
> IResourceStream#close() -
> https://issues.apache.org/jira/browse/WICKET-4600.
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com