Hi, sebb wrote:
> On 18 May 2017 at 19:22, Benedikt Ritter <brit...@apache.org> wrote: >> >>> Am 18.05.2017 um 12:54 schrieb sebb <seb...@gmail.com>: >>> >>> I think the release should be marked as ALPHA. >>> This is because: >>> - there are many unresolved issues >> >> Yes, but I don’t think we could push out 1.0 anyway. >> >>> - it's highly likely that the next release will break compatibility >> >> Why do you think this is the case? Can you give some examples of APIs we >> will likely need to break to move forward? Something that has worked in >> the past is removing those parts for the release as we did for >> commons-text and commons-lang. > > As I recall, there were still a lot of non-private mutable fields. > Encapsulating these will break compat. > > I don't think there is a clear distinction between classes which are > intended to be part of the public API and those which are not. > This increases the risk that a class that is part of the public API > may need to be changed incompatibly. We failed to release for years and the current SNAPSHOT is the de facto API now. So qwe better make this official releasing 1.0 and move on immediately with 2.0 to adjust any stuff that has to be corrected. Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
