java - Cleaning up code breaks binary compatibility -


I am working on a project that I am not being used by many people. We've done a great job to bring down checkstall warnings and this is less because it is going to get binary compatibility without breaking it.

Most of the remaining warnings of constant (public static final) disappeared in the name of the final keyword constants, it becomes clear that the developer had intended to read them only, but they only got to the last Definition was not there.

Unless a developer was writing some pretty awesome code, inspect it, if we add them, their code will not be broken.

The current version number is 1.2.1. Do you apply changes and go to 2.0 or apply it and roll it as 1.3 seems like a very small change for a full 2.0 requirement.

What should I do?

I'm sure you already know this, but I suspect it is "this one Safe / simple / no-worry "upgrade?

  • Point releases are considered safe and routines should include full bug fixes in some projects. Other projects will include new features, if they are not likely to create problems .
  • New major version releases contain evolutionary changes that require optimization
  • The new flagship x.0 version release is highly suspected by sophisticated users It seems that: -)

I think it also depends on how close you are to the next major version release. If this is too soon, do not risk the problematic release of a problem. You can always release a safe point and release an alpha key, but it can be strange if the next big release is released in the future ...


Comments

Popular posts from this blog

MySql variables and php -

url rewriting - How to implement the returnurl like SO in PHP? -

Which Python client library should I use for CouchdB? -