On Thu, Nov 20, 2014 at 8:58 PM, Andrea Del Bene <[email protected]> wrote:
> On 20/11/14 19:56, Andrea Del Bene wrote: > >> My changes imply API breaks, but I think it's worthwhile to take this >> opportunity and clean the inner API before we freeze master branch for >> milestones. >> > I meant release candidates. > For Wicket 6.x there were no Release Candidates. We jumped directly from beta3 to 6.0.0. As we agreed back in the days there is no need of RC because it is the same as a normal release - only bugfixes are possible and no API breaks. >> What do you think? >> > I'd like to release 7.0.0 as soon as possible. To do that I think we should have at least one release of 7.x series without API breaks in it. In my opinion the suggested change is not really needed because no one ever had problems with this. And it is mostly cosmetic one because it is possible to implement custom ICrypt impl without any problems. So I'd prefer if we put this branch on hold. If another API break is really needed for 7.0.0-M5 then merge this branch as well. Otherwise leave it for 8.x. My 2c.
