# Codename One 3.8 Code Freeze, Versioning Changes, and Test Updates

DevFeed: [Codename One 3.8 Code Freeze, Versioning Changes, and Test Updates](<https://devfeed.tech/articles/new-milestones-and-features-19406.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/new-milestones-features/>)

Author: Shai Almog

Published: 2017-10-30T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [releases](<https://devfeed.tech/tags/releases.md>), [travis](<https://devfeed.tech/tags/travis.md>)

## AI overview

Codename One plans a code freeze for version 3.8 and will move from 3.8 directly to 4.0 under a major-version milestone scheme. The post also reports an Eclipse Oxygen simulator issue, an overflow-menu regression fix, automated-test repository integration with Travis CI and GitHub, and the callSeriallyOnIdle method.

## Source excerpt

We will enter code freeze for Codename One 3.8 next week and have a lot of things to clear off the table in order to get there! The first order of business is that there will be no Codename One 3.9... Instead we will go right to 4.0 and switch to major version number update scheme only. This will align us better with industry standards. We spent ages in 3.x and far less in 1.x or 2.x numbering. That doesn't make sense. It's hard to tell what feature is big enough for a "major version number update" and it doesn't indicate as much with the fast pace of releases. So switching to major version numbers in terms of milestones will simplify and give a better indication of the work we put in.