API breakage doesn't sound like a "service" release.|
On 05/23/2013 12:15 PM, Scott Lewis
5/23/2013 4:50 AM, Wim Jongman wrote:
Congratulations guys. Good work.
with respect to the maintenance release, 3.6.1. Since there is
API breakage, and there is now TCK compliance. Would it not be
better to go for 4.0.0?
For the Kepler release (3.6.1), it's too late to shift to 4.0.0.
For major release increments we have to schedule, produce review
materials, and have a release review with the EF...and it's far
too late for that.
As well, because of '1' below...for filetranser and core our 3.6.1
release version already in the platform.
For our next release (whenever that is), we could do 4.0.0...but I
would prefer that we get more/other new stuff in to justify that.
ecf-dev mailing list