Hi, On Wed, Jun 27, 2012 at 12:06 AM, Martijn Dashorst <[email protected]> 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 <[email protected]> > wrote: >> +1 for RC1 >> >> -igor >> >> On Mon, Jun 25, 2012 at 1:17 PM, Martin Grigorov <[email protected]> >> 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
