Prepping for release
23 views
Skip to first unread message
Roberto Alsina
May 21, 2013, 9:02:47 PM5/21/13
to nikola-...@googlegroups.com
Hello folks!
I fixed today a bug that broke Nikola for python 3, and it seems to me
there are no more blockers for another relase.
If anyone thinks differently, now's a good time to let me know!
One thing I am slightly bothered about is that since we moved all JS to
the end of the body, you can't use jquery in the body, so I am leaning
towards keeping *at least* jquery at the head. Any thoughts on that?
I did *not* do the promised importer cleanup because I got too intensely
bored. However, there are a bunch of fixes and improvements in current
master!
Features
--------
* Support --version on "run" command (Issue #504)
* New Turkish translation.
* New MARKDOWN_EXTENSIONS option, defaults to previopus behaviour (Issue
#496)
* Posts with dates in the future will be treated as drafts (Implemented
by punchagan)
* New "TaskMultiplier" plugin category, takes a task, returns 0 or more
new tasks (Issue #483)
* New 'LINK_CHECK_WHITELIST' option for link checker (Issue #477)
* New Croatian translation.
* Jinja-default and jinja-site themes now automatically generated from
the Mako versions.
* New Persian translation
* RSS feed now includes post tags (Issue #462)
* Experimental generic RSS/Atom importer (Issue #347)
* PHP support (Issue #313)
* New PRETTY_URLS option (generates slug/index.html instead of
slug.html) (Issue #429)
* Added "templates/" folder to template path.
* Keyword metadata support in post pages (Issue #451)
Bugfixes
--------
* Customizable teasers were broken (Issue #502)
* Be less invasive when processing rendered HTML (Issue #500)
* Run all tasks that should run (Issue #494, #493)
* Handle timezones in posterous imports (Issue #475)
* Actually ensure LateTasks are run later than Tasks
* Don't add drafts and retired posts to the sitemap (Issue #476)
* Avoid __future__ in setup.py because it breaks buildout (Issue #478)
* Use correct source links with PRETTY_URL=True (Issue #474)
* Handle non-ascii path in bundles (Issue #473)
* Handle non-ascii path in plugin loader (Issue #471)
* Handle non-ascii arguments in main (Issue #470)
* Make sitemap depend on file dates (reported by Kay Hayen)
* Better support for non-ascii urlencoded paths in the wp importer
(Issue #468)
* Avoid crashing if user does a deploy with no commands
* Strip HTML and BODY tags in Post.text() (Issue #464)
* -f option broken in HTML compiler (Issue #463)
* Don't map empty folders, map folders with index.html, and don't map
index.html (Issue #430)
* Wordpress import: write correct redirections for URLs not ending in an
/ (Issue #459)
I fixed today a bug that broke Nikola for python 3, and it seems to me
there are no more blockers for another relase.
If anyone thinks differently, now's a good time to let me know!
One thing I am slightly bothered about is that since we moved all JS to
the end of the body, you can't use jquery in the body, so I am leaning
towards keeping *at least* jquery at the head. Any thoughts on that?
I did *not* do the promised importer cleanup because I got too intensely
bored. However, there are a bunch of fixes and improvements in current
master!
Features
--------
* Support --version on "run" command (Issue #504)
* New Turkish translation.
* New MARKDOWN_EXTENSIONS option, defaults to previopus behaviour (Issue
#496)
* Posts with dates in the future will be treated as drafts (Implemented
by punchagan)
* New "TaskMultiplier" plugin category, takes a task, returns 0 or more
new tasks (Issue #483)
* New 'LINK_CHECK_WHITELIST' option for link checker (Issue #477)
* New Croatian translation.
* Jinja-default and jinja-site themes now automatically generated from
the Mako versions.
* New Persian translation
* RSS feed now includes post tags (Issue #462)
* Experimental generic RSS/Atom importer (Issue #347)
* PHP support (Issue #313)
* New PRETTY_URLS option (generates slug/index.html instead of
slug.html) (Issue #429)
* Added "templates/" folder to template path.
* Keyword metadata support in post pages (Issue #451)
Bugfixes
--------
* Customizable teasers were broken (Issue #502)
* Be less invasive when processing rendered HTML (Issue #500)
* Run all tasks that should run (Issue #494, #493)
* Handle timezones in posterous imports (Issue #475)
* Actually ensure LateTasks are run later than Tasks
* Don't add drafts and retired posts to the sitemap (Issue #476)
* Avoid __future__ in setup.py because it breaks buildout (Issue #478)
* Use correct source links with PRETTY_URL=True (Issue #474)
* Handle non-ascii path in bundles (Issue #473)
* Handle non-ascii path in plugin loader (Issue #471)
* Handle non-ascii arguments in main (Issue #470)
* Make sitemap depend on file dates (reported by Kay Hayen)
* Better support for non-ascii urlencoded paths in the wp importer
(Issue #468)
* Avoid crashing if user does a deploy with no commands
* Strip HTML and BODY tags in Post.text() (Issue #464)
* -f option broken in HTML compiler (Issue #463)
* Don't map empty folders, map folders with index.html, and don't map
index.html (Issue #430)
* Wordpress import: write correct redirections for URLs not ending in an
/ (Issue #459)
Chris “Kwpolska” Warrick
May 22, 2013, 2:34:45 PM5/22/13
to Nikola—Discuss
On Wed, May 22, 2013 at 3:02 AM, Roberto Alsina
<ral...@netmanagers.com.ar> wrote:
> One thing I am slightly bothered about is that since we moved all JS to
> the end of the body, you can't use jquery in the body, so I am leaning
> towards keeping *at least* jquery at the head. Any thoughts on that?
I, for one, would leave jQuery there, just in case. Or,
<ral...@netmanagers.com.ar> wrote:
> One thing I am slightly bothered about is that since we moved all JS to
> the end of the body, you can't use jquery in the body, so I am leaning
> towards keeping *at least* jquery at the head. Any thoughts on that?
alternatively, create an easy interface to append scripts to the end
of <body>.
--
Kwpolska <http://kwpolska.tk> | GPG KEY: 5EAAEA16
stop html mail | always bottom-post
http://asciiribbon.org | http://caliburn.nl/topposting.html
Samat K Jain
May 22, 2013, 9:20:44 PM5/22/13
to nikola-...@googlegroups.com
On 05/21/2013 07:02 PM, Roberto Alsina wrote:
> One thing I am slightly bothered about is that since we moved all JS to
> the end of the body, you can't use jquery in the body, so I am leaning
> towards keeping *at least* jquery at the head. Any thoughts on that?
+1 for loading jQuery in HEAD.
> One thing I am slightly bothered about is that since we moved all JS to
> the end of the body, you can't use jquery in the body, so I am leaning
> towards keeping *at least* jquery at the head. Any thoughts on that?
Though, what happens to those not using the CDN, and using a combined &
minified JavaScript file? Will jQuery be separated out and included at
the top, or will it remain in the concatenated file at the bottom?
--
Samat K Jain <http://samat.org/> | GPG: 0x4A456FBA
Roberto Alsina
May 22, 2013, 9:23:00 PM5/22/13
to nikola-...@googlegroups.com
files, somehow.
Reply all
Reply to author
Forward
0 new messages