Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Configuration changes for jetty-9.4


We don't have a formal policy (we should), but generally we follow:
  • x.y.z release should not break API or configuration. Some API may be added.
  • x.y.0 release may change API, but should not fundamentally change the server.  Minimal config changes.
  • x.0.0 release new architecture, new JVM, new servlet spec, big changes.
So this proposal is a bit of stretch for 9.4.0, but not beyond what we have done before.  If there is a doubt, we can punt to 10.0.x, but that is 6 to 12 months away.

cheers


On 28 April 2016 at 06:50, Cantor, Scott <cantor.2@xxxxxxx> wrote:
>I'm proposing this to go into master, which is currently planned to be a jetty-9.4.x release in the coming months.   But as this is moderately significant change, I'd like to get some community feedback on the value of it, it's impacts and if it should be punted to a 10.0.x release probably early next year.

In light of a similar question about versioning coming up in another dependency of my work recently, can I ask if Jetty has an official versioning policy wrt APIs and configuration formats at this point?

In most of the projects that do have such policies, a three-digit version would tend to imply absolutely no allowance for breaking changes in a minor upgrade, but the more important issue is, IMHO, simply that there be clarity on what's guaranteed and what isn't.

-- Scott

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev



--

Back to the top