On Thursday, June 27, 2019 at 3:33:42 PM UTC-4, Steve Piercy wrote:
>
> No date, but progress is being made.  Check the issue tracker.  We use 
> milestones. 
>

Thanks Steve. I knew about that, but some of those items are very large - 
especially the "possible 2.0 list".

Perhaps I should have been more vague in my question... are there any 
"likely" or "unlikely" timeframes for releases?  As in "most likely not 
until this winter" or "next spring" or "we're hoping for this fall!"

I'm working on pinning the package requirements in anything I maintain to 
"pyramid<2" based on the current deprecations/compatibility items in the 
changelog.  I didn't really think of the changes breaking the pyramid 
ecosystem until someone mentioned a removed API method in a ticket today.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/eda98fc6-430a-40e8-bd97-e787e9262acb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to