Skip to content

Commit 8fdbafd

Browse files
authored
Update README.md
1 parent 6710d6e commit 8fdbafd

File tree

1 file changed

+0
-32
lines changed

1 file changed

+0
-32
lines changed

README.md

Lines changed: 0 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -37,38 +37,6 @@ tests as much as possible. Also [check out the roadmap](https://github.com/prope
3737

3838
Please see our [contribution guideline](http://propelorm.org/contribute.html). Thank you!
3939

40-
## Status of the project
41-
42-
**Never ending alpha releases?**
43-
44-
Propel v2 started as very big refactoring of the old Propel version 1, making it PSR1-2 compatible, introducing namespaces
45-
and refactoring a lot of internal stuff.
46-
However, the heart (and most complex code at the same time) of Propel 1 and 2 is the
47-
[Query](https://github.com/propelorm/Propel2/blob/master/src/Propel/Generator/Builder/Om/QueryBuilder.php)
48-
and
49-
[Object classes builder](https://github.com/propelorm/Propel2/blob/master/src/Propel/Generator/Builder/Om/ObjectBuilder.php),
50-
together 8k unmaintainable lines of code. These 2 files (and with it the architecture) is the main problem why we can not
51-
release a stable version, because it never went stable and due to the lack of contributions (and mean, nobody is surprised
52-
when you look at the very complex structure of those 2 files) we are simply not able to release a version that indicates
53-
that you get somehow support for bugs and new features, which is our aspiration to do so once a official stable version is tagged.
54-
55-
Because Propel2 took so much time (several years) and ActiveRecord (the way it was built in Propel1 and 2) is not modern
56-
anymore (only hardly testable, not so much enjoyable) along with other reasons, we decided to rewrite the very heart of Propel.
57-
The result is [Propel3 a data-mapper](https://github.com/propelorm/Propel3) implementation with optional active-record traits.
58-
It is much cleaner now, is able to support also NoSQL databases and its data-mapper implementation allows you to write tests
59-
in a more enjoyable way. To sum up: A very modern approach that is also designed to work in a high-performance
60-
application-server environment like [PHP-PM](https://github.com/php-pm/php-pm).
61-
62-
In our eyes it makes no sense to tag a Propel2 stable version, because there is simply too less manpower on this very complex
63-
project, we do not want to maintain an old obsolete architecture and want to invest our life time more in a modern approach
64-
of doing ORM in modern PHP.
65-
66-
Our advice:
67-
68-
1. Use Doctrine if you are looking for a long-term supported, full-featured (and difficult to learn) and stable ORM.
69-
2. Use easy to learn Eloquent for prototyping and smaller projects.
70-
3. Help us build Propel3, which aims someday to be both of the above.
71-
7240
## License
7341

7442
See the `LICENSE` file.

0 commit comments

Comments
 (0)