No subject
Sun Dec 12 18:29:16 UTC 2010
number. At the moment I'd see it as 1.7beta or 1.7-rc. One reason is that
this may have an impact on extensions as they can now test for versions of
ckan
>
> * The docs on http://docs.ckan.org/en/latest/ are pulled from the
> branch pointed in pip-requirements.txt, so right now they are built
> from the 1.6.1 release branch. I suggest that when on the master
> branch, we always use 'master' as branch, so the latest docs are built
> from master.
>
>
> Also, what do you think of having a notice in the docs homepage saying
> which version you are looking at? We get quite a few confused users
> looking at the wrong version of the docs.
>
> http://i.imgur.com/bj3Cy.png
>
> This would be a very good idea
Also should things like the API docs point to the docs for the ckan version
not just latest
Toby
The new theme for the docs does not include links to previous
> versions, so I we'd probably need to point to the hovering ones that
> Read the docs adds (not shown on the screenshot, see
> http://docs.ckan.org/en/latest/index.html)
>
>
>
> Adri=E0
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
--e89a8ff1c3d80be3c504be6c8ea3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">2012/4/24 Adri=E0 Mercader <span dir=3D"=
ltr"><<a href=3D"mailto:adria.mercader at okfn.org">adria.mercader at okfn.org=
</a>></span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
Just a little heads up for those who merge a release branch into<br>
master. There are a couple of files that need to be manually edited<br>
after the merge, because they have version numbers on them:<br>
<br>
<a href=3D"https://github.com/okfn/ckan/blob/master/ckan/__init__.py" targe=
t=3D"_blank">https://github.com/okfn/ckan/blob/master/ckan/__init__.py</a><=
br>
<a href=3D"https://github.com/okfn/ckan/blob/master/pip-requirements.txt" t=
arget=3D"_blank">https://github.com/okfn/ckan/blob/master/pip-requirements.=
txt</a><br>
<br>
<br>
It's no big deal, but it may affect a couple of things:<br>
<br>
* The version number on ckan/__init__.py appears in the "Powered by&qu=
ot;<br>
link, so for instance <a href=3D"http://thedatahub.org/" target=3D"_blank">=
http://thedatahub.org/</a> shows 1.6.1b<br>
I'm not sure if we should have a version number in master at all,<br>
maybe 'master' or 'latest' will make clearer that this is t=
he latest<br>
development version. If you prefer a number, it should be the next<br>
major release + 'a' (eg '1.8a'). What do you guys think?<br=
></blockquote><div><br>From my point of view I'd really like master to =
have a valid version number.=A0 At the moment I'd see it as 1.7beta or =
1.7-rc.=A0 One reason is that this may have an impact on extensions as they=
can now test for versions of ckan<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
* The docs on <a href=3D"http://docs.ckan.org/en/latest/" target=3D"_blank"=
>http://docs.ckan.org/en/latest/</a> are pulled from the<br>
branch pointed in pip-requirements.txt, so right now they are built<br>
from the 1.6.1 release branch. I suggest that when on the master<br>
branch, we always use 'master' as branch, so the latest docs are bu=
ilt<br>
from master.<br>
<br>
<br>
Also, what do you think of having a notice in the docs homepage saying<br>
which version you are looking at? We get quite a few confused users<br>
looking at the wrong version of the docs.<br>
<br>
<a href=3D"http://i.imgur.com/bj3Cy.png" target=3D"_blank">http://i.imgur.c=
om/bj3Cy.png</a><br>
<br></blockquote><div>This would be a very good idea<br><br>Also should thi=
ngs like the API docs point to the docs for the ckan version not just lates=
t<br><br>=A0Toby<br><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
The new theme for the docs does not include links to previous<br>
versions, so I we'd probably need to point to the hovering ones that<br=
>
Read the docs adds (not shown on the screenshot, see<br>
<a href=3D"http://docs.ckan.org/en/latest/index.html" target=3D"_blank">htt=
p://docs.ckan.org/en/latest/index.html</a>)<br>
<br>
<br>
<br>
Adri=E0<br>
<br>
_______________________________________________<br>
ckan-dev mailing list<br>
<a href=3D"mailto:ckan-dev at lists.okfn.org">ckan-dev at lists.okfn.org</a><br>
<a href=3D"http://lists.okfn.org/mailman/listinfo/ckan-dev" target=3D"_blan=
k">http://lists.okfn.org/mailman/listinfo/ckan-dev</a><br>
</blockquote></div><br>
--e89a8ff1c3d80be3c504be6c8ea3--
More information about the ckan-dev
mailing list