# Frequently Asked Questions (FAQ)

**URL:** https://forum.openzeppelin.com/t/frequently-asked-questions-faq/140
**Category:** General
**Created:** [December 18, 2018, 6:25pm UTC](https://forum.openzeppelin.com/t/frequently-asked-questions-faq/140 "2018-12-18T18:25:34Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![nventuro](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/nventuro/32/8_2.png) [@nventuro](https://forum.openzeppelin.com/u/nventuro)
#### Post date: [December 18, 2018, 6:25pm UTC](https://forum.openzeppelin.com/t/frequently-asked-questions-faq/140/1 "2018-12-18T18:25:34Z")

</div>

### When will the next version of an OpenZeppelin project be released?

See the OpenZeppelin open-source processes: [Redesigning OpenZeppelin open-source processes](https://forum.openzeppelin.com/t/redesigning-openzeppelin-open-source-processes/2048)

### Where can I find documentation on OpenZeppelin projects?

Documentation for OpenZeppelin projects is at [docs.openzeppelin.com](https://docs.openzeppelin.com/openzeppelin/)

### What does it mean for OpenZeppelin to have a stable API?

See [OpenZeppelin Contracts API Stability](https://forum.openzeppelin.com/t/api-stability/138) for an in-depth discussion of this topic.

### What is the difference between `@openzeppelin/contracts` and `@openzeppelin/contracts-ethereum-package`?

`@openzeppelin/contracts` is set up for general usage, while `@openzeppelin/contracts-ethereum-package` is tailored for being used with [OpenZeppelin Upgrades](https://docs.openzeppelin.com/upgrades/2.7/). This means that its contracts are [already set up to be upgradeable](https://docs.openzeppelin.com/cli/2.6/dependencies#upgrades::writing-contracts.adoc#use-upgradeable-packages).

### Can my project/EIP be added to OpenZeppelin?

We're always open to including new features in the library! Start a new topic under the [OpenZeppelin category](https://forum.openzeppelin.com/c/openzeppelin) describing your feature and why it's a good idea, along with some general use cases and requirements for it.

Accepted features typically go through a short design phase until an API is settled on, at which point we're ready to start taking in [Pull Requests](https://github.com/OpenZeppelin/openzeppelin-solidity/pulls). Opening a PR before said design is final is discouraged, since usually some discussion is required before a merge, which often means refactoring the proposed code.