Inform about the current roadmap / plans in the blog

[motin]

I see Propel3 is now the active repo, replacing Propel2. Care to outline what is going on in propel dev camp? :)

The information that is available is in Propel3's active repo: "Version 3 of Propel ORM replaces Propel2, which is not maintained anymore. Propel3 introduces a data-mapper implementation which separates your entities from the actual persisting logic."

I'll assume that the data-mapper branch of Propel2 effectively was forked off into the new repo Propel3, but there is no information or background explanation on http://propelorm.org/blog/

Such a (it can be short) blog post can really help plan how one should plan migration / contributions to propel going forward.

Thanks :)

[motin]

In the related issue https://github.com/propelorm/Propel2/issues/1297, @marcj explains "Please read #795. Very detailed explained, why there will be no unmaintained Propel2, just to move data-mapper to Propel3."

This is confusing, a blog post would definitely help clarify what is going on.

[marcj]

I completely agree :) Unfortunately currently bad timing, but I'll do it soon.

[motin]

@marcj What about just putting a blog post like "This blog is no longer used to convey updates about the project, check the issues at Github for the latest developments" OR reach out to the other contributors that are in the loop and see if someone has the time to write a blog post? The last post is from two years ago, it looks to newcomers that the propel project is vaporware.

[motin]

Any updates?

[motin]

@marcj Any updates? I no longer use PHP but I am curious about what is going on with Propel. Maybe someone else is.

[peter-mghendi]

@motin I'm curious too, and I use PHP actively. Finding an ORM to use independently of a framework is becoming a chore.