Melange packages are no longer suffixed with date.

JavascriptCSSDependencies.wiki

diff --git a/JavascriptCSSDependencies.wiki b/JavascriptCSSDependencies.wiki
index 45aa550..f08356f 100644
--- a/JavascriptCSSDependencies.wiki
+++ b/JavascriptCSSDependencies.wiki
@@ -1,5 +1,5 @@
 #summary Javascript and CSS dependencies loading in Melange
-#labels Phase-Design,Contents-Draft,Importance-Featured
+#labels Phase-Implementation,Contents-Complete,Importance-Featured
 
 = Introduction =
 
@@ -62,7 +62,7 @@
 The *tc(script_path, context)* method is actually a shortcut for *melange.dependency.templateWithContext(script_path, context)*. This has been renamed for conveniency.
 This method will take care of downloading the script related to the template, evaluate it and then it will inject the context.
 This was formerly done using the {{{ melangeContext }}} attribute of the script tag. So now there is no need to convert the JSON object to a string for the attribute, but you can just put the plain JSON file inside the context parameter of this function calling.
-All the {{{ tc() }}} calls are *synchronous*. This means that it automatically evaluates itself as {{{ [null, tc(), null] }}}. The reason to do this is because there is no way for JS scripts to know about their context in the page (e.g. pass some parameters from the Django template to the JS scope), so we need a small hack to make them so and attach them a context. When a JS template is loaded, it will register itself in a global "template queue" hosted in the main _melange-YYMMDD.js_ file, in the _melange.templates_ object. The context is then attached to the *last* template that has been registered. So we can't allow another template to be attached before the former one has been coupled with a context.
+All the {{{ tc() }}} calls are *synchronous*. This means that it automatically evaluates itself as {{{ [null, tc(), null] }}}. The reason to do this is because there is no way for JS scripts to know about their context in the page (e.g. pass some parameters from the Django template to the JS scope), so we need a small hack to make them so and attach them a context. When a JS template is loaded, it will register itself in a global "template queue" hosted in the main _melange.js_ file, in the _melange.templates_ object. The context is then attached to the *last* template that has been registered. So we can't allow another template to be attached before the former one has been coupled with a context.
 
 === function() ===