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
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
Hello,
Because of how the wicketstuff-core release process works there is the
possibility that the current wicket upstream contains changes that are
different from the latest stable wicket release.
When I create a release branch I do so at the top of the present
development branch
Michael, could you better explain what exactly happened? I'm not an expert
on Git, but I really want to understand what to do.
Thanks,
PS: and thank you very much. You've been doing a great job at keeping
wicketstuff alive and functional... :-)
Bruno Borges
www.brunoborges.com.br
+55 21
