On 11 May 2011 14:51, Jochen Wiedmann <[email protected]> wrote: > On Wed, May 11, 2011 at 3:45 PM, sebb <[email protected]> wrote: > >> However, if a breaking API change is needed, then the package >> name/Maven ids will *have* to be changed. > > That's not different from a new major release in commons. If you > anticipate the necessity of binary changes, consider creating a > maintenance branch and a new branch anyways.
+1, but my concern is not about SVN branches. > >> Depending on incubator code is akin to depending on alpha code, i.e. >> the user should be prepared for API instability. > > Why so? Since incubation generally means new eyes looking at the code, it seems likely that any API problems are quite likely to be found in incubation. Probably more so than afterwards. > In contrary, I'd suggest to have the "early release" based on > a stable branch for that very reason. But if problems are found with the API, there is no such thing as a stable branch. > > -- > I Am What I Am And That's All What I Yam (Popeye) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
