Hello,
With the first milestone of wicket 1.5 released there has been some
interest expressed for a corresponding wicketstuff-core branch.
Because wicket 1.5 is basically experimental right now I'm not sure if
switching trunk to track it is the best idea.
But eventually trunk will track 1.5, probably at the release candidate
stage.
However, I'm willing to implement the consensus opinion on this.
Structure Options:
[ ] - trunk to track 1.5, branch for 1.4.11-SNAPSHOT and subsequent
releases. (+:no merge later; -: trunk will be broken for an extended period)
[ ] - trunk stays on 1.4.x, create new branch to track 1.5-M1. (+: no
switch is needed; -: at some point need to merge the branch back into trunk)
Wicket 1.5 Options:
[ ] wicket 1.5 branch is set to wicket 1.5-M1, hard code to the released
milestone and increment with each new version until the 1.5 release.
[ ] wicket 1.5 branch is set to wicket 1.5-SNAPSHOT and if there is
demand we can cut releases to match the wicket milestones and/or release
candidates.
I'll wait until Monday night (eastern time) before making any changes
based on the vote.
Thanks,
Mike
