Skip to content
BENIBIX Learn

Product & Releases

Features, licensing and shipping · 35 terms

Sort
Compare

Releases

14

Handing a version to users: how it is numbered, what may break, and the kinds of release in between.

A version of your app that you hand to users. It has a number.

A small, quick release that fixes one big bug in the live app.

An early version. Some users try it before the final one.

A version the makers promise to keep safe for years.

An early, rough version for the team and a few testers. Expect bugs and missing parts.

A version that may be the final one, if tests find no big bugs.

Version numbers in three parts. They say how big a change is.

A change that makes code built on the old version stop working.

When a new version still works with things made for the old one.

Marking a feature as on its way out. It still works for now.

A newer copy of a program. It fixes bugs, shuts safety holes or adds new things.

A small update that shuts a safety hole in an app. It is made to put in fast.

The last day an app version gets fixes. After it, new safety holes stay open.

Version numbers made from the release date, like 24.04 for April 2024.

Software Licenses

17

The legal rules for using code, the open and closed kinds of software, and the common licenses.

The legal text that says what others may do with your code.

A license with few rules. Keep the notice, and use the code as you like.

A short open source license. You may do almost anything if you keep the notice.

An open source license like MIT. It adds a promise about patents.

A short permissive license. Keep the notice, and do not use the authors' names to sell.

A rule in some open licenses. If you share a changed copy, its code must stay open.

An open source license. Changes you share must stay open source too.

Like the GPL. But if you run your changed copy as a web app, you must share the code.

A copyleft rule made for libraries. Your app can stay closed. Fixes to the library get shared.

A weak copyleft rule that works one file at a time. A changed MPL file stays open.

A license that lets you read the code but limits how you use it. It is not open source.

Software whose code anyone may read, use, change and share.

Software whose owner keeps the code secret. You can use it, not change it.

One code base, two licenses to pick from. Often one is free and open, and one is paid.

A form you sign so a project can use your code. It can then change the terms.

A short, fixed name for a license, like MIT or Apache-2.0, that tools can read.

Can code with two sets of rules go in one app? This is the answer.

Documentation

4

The writing that explains a project, from its front page to the list of what each release changed.

The writing that explains how to use, set up or change software.

The first file you read in a project. It says what the project is for.

A file that lists what changed in each release. The newest is at the top.

A file that tells people how to help with a project. It covers bugs and code.