I'm looking into updating getting started a bit, but is stuck before even beginning: 1. Looking at boost.org, I don't actually see any link to "Getting Started". Have I missed it? 2. I don't see getting started in checkout of https://svn.boost.org/svn/boost/website/public_html/beta I presume it still lives in more/getting_started.html. Ok, good. If I change it, will the changed version appear either boost.org, or beta.boost.org ? - Volodya
Vladimir Prus wrote:
I'm looking into updating getting started a bit, but is stuck before even beginning:
1. Looking at boost.org, I don't actually see any link to "Getting Started". Have I missed it?
I couldn't find it at first either. There is a link at the left of the main boost.org page under GETTING STARTED. It links to: http://www.boost.org/doc/libs/release/more/getting_started/index.html KevinH -- Kevin Heifner heifner @ ociweb.com http://heifner.blogspot.com Object Computing, Inc. (OCI) www.ociweb.com
Kevin Heifner wrote:
Vladimir Prus wrote:
I'm looking into updating getting started a bit, but is stuck before even beginning:
1. Looking at boost.org, I don't actually see any link to "Getting Started". Have I missed it?
I couldn't find it at first either. There is a link at the left of the main boost.org page under GETTING STARTED. It links to:
http://www.boost.org/doc/libs/release/more/getting_started/index.html
Well, indeed. I really think it should be added to the navigation bar too. Question 2 still stands :-) - Volodya
On 09/04/2008, Vladimir Prus <ghost@cs.msu.su> wrote:
Well, indeed. I really think it should be added to the navigation bar too.
I agree, the navigation bar could do with a little work. I'll post something about that to the documentation list soon.
Question 2 still stands :-)
The answer's no, the same for all documentation included in the distribution. Daniel
Daniel James wrote:
On 09/04/2008, Vladimir Prus <ghost@cs.msu.su> wrote:
Well, indeed. I really think it should be added to the navigation bar too.
I agree, the navigation bar could do with a little work. I'll post something about that to the documentation list soon.
Question 2 still stands :-)
The answer's no, the same for all documentation included in the distribution.
Ok. Can this be changed, please? - Volodya
Vladimir Prus wrote:
I presume it still lives in more/getting_started.html. Ok, good.
You need to edit more/getting_started/*.rst.
If I change it, will the changed version appear either boost.org, or beta.boost.org ?
The answer's no, the same for all documentation included in the distribution.
Ok. Can this be changed, please?
It's not in my control. But it certainly shouldn't be updated from trunk, since that documents trunk and not the current release. That would prevent updating it for any new changes that don't apply to 1.35. I suppose we could update the site documentation from the release branch, if that is considered acceptable by the release manager. Although that could end up with the situation we had before when there were basically three different versions of the website - one in trunk, one in release, and one online. These were often out of sync and a pain to merge. The new website organisation wasn't designed out of malice. Daniel
Daniel James wrote:
Vladimir Prus wrote:
I presume it still lives in more/getting_started.html. Ok, good.
You need to edit more/getting_started/*.rst.
OK.
If I change it, will the changed version appear either boost.org, or beta.boost.org ?
The answer's no, the same for all documentation included in the distribution.
Ok. Can this be changed, please?
It's not in my control. But it certainly shouldn't be updated from trunk, since that documents trunk and not the current release. That would prevent updating it for any new changes that don't apply to 1.35.
I suppose we could update the site documentation from the release branch, if that is considered acceptable by the release manager. Although that could end up with the situation we had before when there were basically three different versions of the website - one in trunk, one in release, and one online. These were often out of sync and a pain to merge. The new website organisation wasn't designed out of malice.
From my standpoint, there should be a way to clarify getting started so that users of the current release can see updated copy on the website. If any fixes will appear only in the next release, they won't benefit users now.
- Volodya
participants (3)
-
Daniel James -
Kevin Heifner -
Vladimir Prus