Re: [Python-Dev] Doc nits question
Terry Reedy schrieb: > Georg Brandl wrote: >> Fred Drake schrieb: >>> On Oct 2, 2008, at 9:21 AM, Georg Brandl wrote: I intend to set things up so that the docs at docs.python.org are continually rebuilt, just like the /dev docs were until now. > > Will you do the same for the 3.0 version? > http://docs.python.org/dev/3.0/ Yes. Nothing has changed there. > The following page has no reference to the 3.0 version > http://www.python.org/doc/versions/ > The 'unreleased' link at the top goes to a link that only referenced the > SVN version and not the built version above. Adding a link to the build > version would have made it easier to find ;-). http://www.python.org/dev/doc/, where the link leads to, references both trunk and 3.0 here. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
On Thu, Oct 2, 2008 at 6:21 AM, Georg Brandl <[EMAIL PROTECTED]> wrote: > Jesse Noller schrieb: >> So, we just released and there are a few doc typo bugs being filed - >> my question is if all doc-fixes have to wait for 2.6.1/2.7 or if we >> can hotfix the 2.6 docs? > > I intend to set things up so that the docs at docs.python.org are continually > rebuilt, just like the /dev docs were until now. The 2.6 docs are now updated similar to how 2.5 was (hourly). 2.5 docs are no longer updated. In case you can't guess the url, it's: http://docs.python.org/dev/2.6/ 3.0 should continue to work. Let me know if you have any problems. n > > Georg > > -- > Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. > Four shall be the number of spaces thou shalt indent, and the number of thy > indenting shall be four. Eight shalt thou not indent, nor either indent thou > two, excepting that thou then proceed to four. Tabs are right out. > > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/nnorwitz%40gmail.com > ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
Georg Brandl wrote: Fred Drake schrieb: On Oct 2, 2008, at 9:21 AM, Georg Brandl wrote: I intend to set things up so that the docs at docs.python.org are continually rebuilt, just like the /dev docs were until now. Will you do the same for the 3.0 version? http://docs.python.org/dev/3.0/ The following page has no reference to the 3.0 version http://www.python.org/doc/versions/ The 'unreleased' link at the top goes to a link that only referenced the SVN version and not the built version above. Adding a link to the build version would have made it easier to find ;-). All Sphinx-generated pages currently have a "last update on:" in the footer. Do you think that suffices for this purpose? It certainly would limit a search for closed issues not incorporated in the update (to avoiding duplication). ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
On Oct 2, 2008, at 1:17 PM, Georg Brandl wrote: All Sphinx-generated pages currently have a "last update on:" in the footer. Do you think that suffices for this purpose? Yes, I do. -Fred -- Fred L. Drake, Jr. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
Fred Drake schrieb: > On Oct 2, 2008, at 9:21 AM, Georg Brandl wrote: >> I intend to set things up so that the docs at docs.python.org are >> continually >> rebuilt, just like the /dev docs were until now. > > Wonderful! This should help avoid repeat reports of simple typos. > > At one point, we started to separate the documentation releases so > that update releases could be easily pushed at times when there wasn't > a corresponding Python release. There are a couple of examples of > these in the specific-versions list, IIRC. These have version numbers > ending with "p1" (for patch 1; no more than one patched version was > ever released for any particular Python version). > > It may be worth trying this or something like it again as well, if > there's enough volunteer time available. Such versions would need to > be clearly marked on every page as to when they were updated, so that > readers can tell if they have the latest update. All Sphinx-generated pages currently have a "last update on:" in the footer. Do you think that suffices for this purpose? Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
On Oct 2, 2008, at 9:21 AM, Georg Brandl wrote: I intend to set things up so that the docs at docs.python.org are continually rebuilt, just like the /dev docs were until now. Wonderful! This should help avoid repeat reports of simple typos. At one point, we started to separate the documentation releases so that update releases could be easily pushed at times when there wasn't a corresponding Python release. There are a couple of examples of these in the specific-versions list, IIRC. These have version numbers ending with "p1" (for patch 1; no more than one patched version was ever released for any particular Python version). It may be worth trying this or something like it again as well, if there's enough volunteer time available. Such versions would need to be clearly marked on every page as to when they were updated, so that readers can tell if they have the latest update. -Fred -- Fred L. Drake, Jr. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
Jesse Noller schrieb: > On Thu, Oct 2, 2008 at 9:21 AM, Georg Brandl <[EMAIL PROTECTED]> wrote: >> Jesse Noller schrieb: >>> So, we just released and there are a few doc typo bugs being filed - >>> my question is if all doc-fixes have to wait for 2.6.1/2.7 or if we >>> can hotfix the 2.6 docs? >> >> I intend to set things up so that the docs at docs.python.org are continually >> rebuilt, just like the /dev docs were until now. >> >> Georg > > Fantastic, so the doc updates should go to the 2.6 branch, correct? > (Not that I'm suggesting checking in all willy nilly) This is another thing that needs to be discussed: how to handle backports between 2.6 and 2.7. Up to now, we backported changes from trunk to maint manually, but after the experience we've had with svnmerge, I see several possibilities: 1. Do bugfixes in maint, merge them to trunk via svnmerge. This has the drawback that you have to work in two different repos for fixes vs. new features. The advantage however is that normally all fixes that go into maint apply to trunk as well, so almost no blocks need to be done. However, since Py3k merges are done from trunk, the 3k merge will see merges as single commits, so they aren't easy to block if not applicable. This will mean more conflicts. 2. Do bugfixes in trunk, and merge them to maint via svnmerge. Arguments as for 1, but reversed: many blocks, but less problems with 3k. 3. Backport bugfixes manually, like for the previous maintenance branches. cheers, Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
Jesse Noller wrote: > So, we just released and there are a few doc typo bugs being filed - > my question is if all doc-fixes have to wait for 2.6.1/2.7 or if we > can hotfix the 2.6 docs? Well the fixes can definitely all go in to SVN on both the trunk and the maintenance branch. As to when we update docs.python.org from the maintenance branch... I believe historically it has only been done at each new maintenance release, but I don't see any fundamental problems with the idea of updating it more frequently. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
On Thu, Oct 2, 2008 at 9:21 AM, Georg Brandl <[EMAIL PROTECTED]> wrote: > Jesse Noller schrieb: >> So, we just released and there are a few doc typo bugs being filed - >> my question is if all doc-fixes have to wait for 2.6.1/2.7 or if we >> can hotfix the 2.6 docs? > > I intend to set things up so that the docs at docs.python.org are continually > rebuilt, just like the /dev docs were until now. > > Georg Fantastic, so the doc updates should go to the 2.6 branch, correct? (Not that I'm suggesting checking in all willy nilly) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Doc nits question
Jesse Noller schrieb: > So, we just released and there are a few doc typo bugs being filed - > my question is if all doc-fixes have to wait for 2.6.1/2.7 or if we > can hotfix the 2.6 docs? I intend to set things up so that the docs at docs.python.org are continually rebuilt, just like the /dev docs were until now. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
