://www.nabble.com/-vote--Name-the-release-after-1.3-tf3603749.html#a10245158
Sent from the Wicket - Dev mailing list archive at Nabble.com.
[ ] Apache Wicket 1.4
Binding: Al Maw
Non binding: Jean Baptiste Quenot, Charlie Dobbie
3 +1
[ ] Apache Wicket 1.5 (after the JDK)
Binding: Johan
Non Binding: Erik van Oosten
2 +1
[ ] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor change)
Binding: Martijn, Igor, Frank,
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org
--
View this message in context:
http://www.nabble.com/-vote--Name-the-release-after
[] Apache Wicket Omega
i see most are voting for wicket 2.0 are we sure about that?
i think it won't even be that big api break (i really think it will be much
less then 1.2 - 1.3)
and it will be still very close to what we call now 2.0.. so it could be
confusing in the short term.
so mostly it
* Martijn Dashorst:
Apache Wicket 1.3 will be followed by:
[x] Apache Wicket 1.4
[ ] Apache Wicket 1.5 (after the JDK)
[ ] Apache Wicket 5 (similar, but more accurate)
[ ] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor change)
[ ] Apache Wicket 2007
[ ] Apache Wicket r59332
Wednesday, April 18, 2007, 11:04:12 PM, Martijn wrote:
There is a vote already in place for switching the development
branches around. Now it is time to name the release after 1.3 (and not
1.3.1 :).
Apache Wicket 1.3 will be followed by:
[+1] Apache Wicket 2.0 (i.e. becomes our old 2.0
[x] Apache Wicket 1.4 (Non-binding vote)
Having declared 2.0 a dead-end, you shouldn't release anything with
the same version number within six months at least - there's too much
potential for confusion IMHO. Not to mention tutorials and code
snippets that are floating around labelled for
its not just an api break. it is also the fact that we changed the
underlying technology. ive seen a lot of projects jump a major version when
they switched to jdk 1.5 without adding too many features.
it will also make it easier for martijn and eelco to continue with their
book as they dont
Charlie Dobbie wrote:
[x] Apache Wicket 1.4 (Non-binding vote)
Having declared 2.0 a dead-end, you shouldn't release anything with
the same version number within six months at least - there's too much
potential for confusion IMHO. Not to mention tutorials and code
snippets that are floating
On 19.4.2007, at 1.04, Martijn Dashorst wrote:
Apache Wicket 1.3 will be followed by:
[x] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor
change)
[x] Apache Wicket 7.05 - I'm an Ubuntu user... :D
On 4/19/07, Janne Hietamäki [EMAIL PROTECTED] wrote:
On 19.4.2007, at 1.04, Martijn Dashorst wrote:
Apache Wicket 1.3 will be followed by:
[x] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor
change)
--
Bruno Borges
Summa
There is a vote already in place for switching the development
branches around. Now it is time to name the release after 1.3 (and not
1.3.1 :).
Apache Wicket 1.3 will be followed by:
[ ] Apache Wicket 1.4
[ ] Apache Wicket 1.5 (after the JDK)
[ ] Apache Wicket 5 (similar, but more accurate)
[ ]
Apache Wicket 1.3 will be followed by:
[X] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor change)
Martijn
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket
On 4/19/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
[ ] Apache Wicket XP Vista 2007
[x] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor change)
Frank
14 matches
Mail list logo