I'm all for only changes the packages for 2.0. I still would like to
keep the breaks for 1.3 minimal, and generally get it over with asap.
Doing it just before the first public release sounds fine to me.
me tooo..
doing it as late as possible.
but can we do it after 30th of nov ;) (looking
On 11/13/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Before we start a vote for renaming our package structure, I think we
should carefully consider the consequences.
The proposal is to rename our wicket.* package to org.apache.wicket.*
There is no requirement within Apache to do so, but it
yeah, what eelco said.
-igor
I'm all for only changes the packages for 2.0. I still would like to
keep the breaks for 1.3 minimal, and generally get it over with asap.
Doing it just before the first public release sounds fine to me.
Eelco
yeah +1 to that
On 11/13/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
yeah, what eelco said.
-igor
I'm all for only changes the packages for 2.0. I still would like to
keep the breaks for 1.3 minimal, and generally get it over with asap.
Doing it just before the first public release
+1
Juergen
On 11/13/06, Frank Bille [EMAIL PROTECTED] wrote:
yeah +1 to that
On 11/13/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
yeah, what eelco said.
-igor
I'm all for only changes the packages for 2.0. I still would like to
keep the breaks for 1.3 minimal, and generally get it
