Hi, > Andreas Lehmkühler <andr...@lehmi.de> hat am 6. Juli 2015 um 11:55 > geschrieben: > > > Hi, > > > I'd like to do a 2.0.0 release rather sooner than later and I guess I'm not > the > only one ;-) > > We are down to 24 issues marked with "Fix Version 2.0.0". > > @Assignees: please have a look at "your" issues and verify if we really should > wait for them to be resolved first or if those could be moved to a later > release > (2.1.0 or 3.0.0) > > To start with a release candidate would be another option, but I'd prefer to > release 2.0.0. > > WDYT?
As there seems to be a majority supporting a release candidate I'd like to find out what exactly a possible RC would be so that we are all on the same page: - is it feature complete? IMHO, yes - is the api stable? IMHO, yes - do we create a branch or just release from a tag? IMHO, we should branch, especially if the api is meant to be stable - we won't push the RC to maven central but would provide a possibility to download the RC. This is a common approach in other apache projects How long do we wait until releasing the final 2.0? We might define some rule/goal for that. What exactly will be the difference between the RC and the final release? (there are not that much open tickets left, so that I presume it won't be that big) I'm in favour of a final release without an RC. Our release process is quite lean so that it wouldn't hurt to much to release a 2.0.x bugfix release. BR Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
