> I couldn't find anything in the docs or issue tracker.
>
> I'm wondering how much time I have to create 2.0 compatible versions of
> some libraries.
>
------------------------
Steve Piercy, Eugene, OR
Jonathan Vanasco
unread,
Jun 27, 2019, 5:43:40 PM6/27/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to pylons-discuss
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.