[
https://issues.apache.org/jira/browse/WICKET-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783057#comment-13783057
]
Paul Bors commented on WICKET-5321:
-----------------------------------
Then having the guide against the latest version is fine as long as for each
migration there is a chapter (or at least migrating from the last major
version).
My first migration was from a Wicket 1.3.x to 1.5.x and I had to read all
migration wiki pages that I aggregated into a single doc and spread it out into
different tasks that my team and I had to go through to migrate over the entire
project. Wasn't a pleasant mini-project but we did it!
I'm not sure if the migration doc really belongs in this guide because of 2
reasons I can think of:
# That chapter on migrating will keep growing over time
What would happen with older migration guides?
# It would be harder for the community to add new sections to the migration as
they run into them
A wiki is easier to edit and contribute to that this guide that requires
code to be checked out, create patches, push requests and etc.
> Incorporate Wicket Guide into website
> -------------------------------------
>
> Key: WICKET-5321
> URL: https://issues.apache.org/jira/browse/WICKET-5321
> Project: Wicket
> Issue Type: Bug
> Components: site
> Reporter: Martijn Dashorst
> Attachments: grails-generator.zip, Wicket free guide_asf.odt, Wicket
> free guide.odt
>
>
> Andrea del Bene has donated the Wicket Guide to the Apache Software
> Foundation. This issue will track the progress into incorporating the
> document into our website.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
