Hi all,
Can I get commit access for wicketstuff, so I can continue working on wicket-
security?
Best regards,
Emond Papegaaij
Wow... got it. Thanks for clarifying all of this.
Now, I think it is hard to guarantee no one will push API changes + features
on a unique commit.
Shouldn't we consider to stop building for point releases and only release
after a stable Wicket version? (ie. not RC's)
Bruno Borges
www.brunobor
Hi Bruno,
Actually everything was fine with the 1.5-rc2.1 release but I just
wanted to make sure that future releases would be trouble free as well.
This is just a possible edge case issue when doing point releases (it
does not apply for the first release on a given wicket release).
This is
Hi,
I would like to add wicket-eidogo player [1] to wicketstuff, but :
1. Is it a good idea ? I did not find information about which project
can be part of wicketstuff or not. Any definition of wicketstuff's
vision somewhere ?
2. I never used git before (CVS, SVN, Synergy), is it better to fork
