Hi folks, Since the last status update I gave maybe a month or so ago, where I enumerated the list of "must-haves" for a 1.0beta Pyramid release (see <http://groups.google.com/group/pylons-devel/browse_thread/thread/c0d56e164886c253/5f880003fbd18797>), we've had two more alpha releases (1.0a8 and 1.0a9) that more or less killed the "must-have" and "should-have" items listed in that status report. The changes made in those releases can be seen here: http://docs.pylonshq.com/pyramid/dev/changes.html
New niggly things keep popping up and replacing the issues we swat down, of course. Here's the current "must-have" punchlist: Must-Have (before 1.0) ---------------------- - Write a "Whats New" (delta from BFG 1.3) - API docs for ``pyramid.views.action``. (also, @action decorator uses ``name`` for the method name; consider whether this will be confused with ``name`` of ``view_config`` which means something else) - Add docs for ``__action_decorator__`` attr of handler. - Use a commit veto when configuring repoze.tm2 in paster templates for non-1X, 2X, or 3X responses. - Figure out how to slim the herd of paster templates. Related: https://github.com/Pylons/pyramid/issues#issue/40, https://github.com/Pylons/pyramid/issues#issue/42, https://github.com/Pylons/pyramid/issues#issue/44, https://github.com/Pylons/pyramid/issues#issue/94 , https://github.com/Pylons/pyramid/issues#issue/95 - Explain how to use i18n localization in Mako and Jinja2. - Turn Forbidden status code into a 403 (it's currently a 401, which is for bw compat, but is misleading). - Fix too-long template lines in tutorials for PDF renderings. - Bug in URL dispatch pattern matching: https://github.com/Pylons/pyramid/issues#issue/90 - Allow ``pyramid.security.remember`` to accept a list of tokens for use when there's an ``auth_tkt`` authentication policy: https://github.com/Pylons/pyramid/issues#issue/81 and https://github.com/Pylons/pyramid/issues#issue/78 - Add docs for ``route_path`` and ``route_url``, etc to Request API docs (see also https://github.com/Pylons/pyramid/issues#issue/19). By far, the hardest task on this list is "slim down the herd of paster templates". The idea behind this is to have Pyramid ship with fewer paster templates (ideally just one single example template), and depend on third-party paster templates shipped in external packages which have their own release cycles and "opinions", so we don't need to maintain and document as many templates (and their attendant contexts and opinions) within the core. I'd like to be able to freeze feature development on the Pyramid trunk in preparation (and perhaps a docs printing) for a first beta by the end of January. We'll see how it goes. - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
