Djangae 1.0.0 Released!

[Luke Benstead]

Hi everyone!

It's finally time to tag Djangae 1.0.0!

Djangae has been stable for a long time now, and really we should've given Djangae a 1.0 release years ago! There was always another bug to fix, or another feature we wanted though and so leaving it in a continuous "it's almost ready!" state is what happened.

But now work is progressing on bringing Djangae up-to-date with the latest Python and Django releases, it's now time to break compatibility, make things temporarily unstable and recognise the current Djangae as the stable project that it is.

So, what's next?

Djangae is going to be stripped back. App Engine on the Python 3 runtime is very different and as a result Djangae 2.x will be a completely different series also.

Many of the djangae.contrib apps are going to disappear, perhaps all of them! There's no eventual consistency on the new Datastore, there's no Users API, there's no memcache.

The Datastore connector is being moved into its own project, that can be used from any Django application.

We'll do what we can to smooth the upgrade process as much as possible, but it's not going to be a drop-in replacement for current Djangae unfortunately, and it may take a while to get to a state where an upgrade process is documented. When we're done though, Djangae will be better, simpler and cleaner.

Also the Djangae 1.x series will still receive bug fixes, and the occasional bug-fix release will still happen.

Thank you!

Thanks to everyone that has contributed to Djangae over the past 5 or 6 years. The road to Djangae 1.0.0 has been a long one, but here's to a future in Djangae 2.x!

--

--

Luke Benstead - Tech Director p.ota.to

[Jacob G]

Thanks Luke and all for your tremendous contributions over the years to the community! A lot of people have found great value in your work.

Do you have in mind djangae functionality outside the data connector? e.g.:

• deferred tasks
• shard processing
• pipeline processing

Although there's potentially other ways to accomplish these things, such as Cloud Dataflow, it's sometimes easier to do things directly in the django app when tasks are tightly coupled, and it runs faster than triggering dataflow vm's to start up.

[Luke Benstead]

The plan is to first strip it right back to deferred tasks, and whatever backends / settings are necessary to get Django playing nice (e.g. sorting out logging, cache backend, mail backend etc.), and then start adding stuff back in where it makes sense. Switching gauth to OAuth/IAM will be an early focus.

There's about to be a lot of code deletion in master - so brace yourself :)

--
You received this message because you are subscribed to the Google Groups "djangae-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to djangae-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/djangae-users/4bb5f472-26e4-46fe-abce-54616080c31a%40googlegroups.com.

[pdoherty]

Congratulations to the Djangae team! Thanks for releasing and (actively!) supporting such a useful project.

PRD

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

To view this discussion on the web, visit https://groups.google.com/d/msgid/djangae-users/CAArNv2%2BF%2BsFfOXuRubhU%2BAZ%3DFfmfuVxYLC8Lc%2B%2B110ic_X%2Bj%3Dg%40mail.gmail.com.