I'm interested in a) getting developer access to the SVN system - if I don't already have it. b) I don't know if the SVN system has a web browser interface like the CVS system did. If it does it would be nice to have it enabled. Personally, since i have tortoise svn on my machine, its not a big deal if I don't have it. But I think its very useful for those who arn't hooked up to SVN system to be able to observe history and when investigating features. c) It seems to me that information regarding SVN access and boost customs and practices for using it to best advantage should be available form the main boost web page. Oh now I found it - its via a link titled Sandbox SVN. So I guess what I'm ask is for the main page to be tweaked so it's location is more obvious. d) The same goes for Trac. There is a link referring to it as a list of bug fixes. But it seems that its also intended to be used for reporting bugs. I don't think that's at all clear from the main page. e) Poking around with the browser shows me a branch for RC_1_34_0. It seems we're releasing 1.34.1 - where is the branch for the actual code released? or are they the same? or? f) Poking around a little more, I see: root/branches/SPIRIT_1_6/boost/boost ... // all the boost headers which is what I expect to see. I presume that all these headers are the state at the time the branch was made plus any merged in updates. OK then I look at: root/branches/SPIRIT_1_6/boost/libs ...// only find the directory for spirit which kind of surprises me. I expect to see the whole set of libraries even though I know they havn't changed on this branch. I'm sure all the boost libraries haven't changed on this branch yet they are all there. What am I missing here? On the web page http://svn.boost.org/trac/boost/wiki/BoostSubversion under Developer Access one finds: " Boost contributors are given read/write access to the Boost Subversion repository when their Boost tasks warrant. There are three different areas of the Boost Subversion repository that contributors may need access to: a.. The main Boost development areas, including the devel and stable directories. This level of access is typically restricted to authors and maintainers of Boost libraries. *** What is are the "devel" and "stable" directories? Is one of them the "trunk" Please expand upon this. a.. The sandbox area, which is used to develop new libraries and tools that have not yet come up for Boost review. This level of access is available to contributors who want to develop future Boost libraries and collaborate with other Boost contributors. b.. The web site, which stores the Boost web site. To gain developer access to the Boost Subversion repository, please send a email to the Boost Moderators at boost-owner -at- lists.boost.org stating why you need write access to the Boost Subversion repository, and which parts of the repository--boost itself, the sandbox, or the web site--you need access to. *** How can I find out what parts (if any) I have developer access to. When I downloaded the SVN trunk the first time - I wasn't asked for a password - which surprised me. I didn't try to check anything in so I have no idea what kind of access I had. If you had access to Boost CVS when it was hosted at SourceForge, please provide your SourceForge user ID. Once a moderator has approved you for access to the Subversion repository, you will receive an invitation via e-mail that asks you to provide a user name and a password, which will be used to access both the Boost Subversion repository and the Boost Trac. *** I went through some procedure to get developer access to boost trac - so I have a password for that. So am I already in business for SVN? You will also be asked to grant permission for your past and future Boost contributions to be licensed under the Boost Software License version 1.0 and future versions: your permission is required to work with the Boost Subversion repository, so that we can ensure that Boost code is licensed under the Boost Software License. Once you have signed in, you should notify the moderator of your username, and he will complete the process. Thanks in advance. Robert Ramey
on Sat Aug 11 2007, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
I'm interested in
a) getting developer access to the SVN system - if I don't already have it.
You already have it. Read http://svn.boost.org/trac/boost/ "Getting a Trac/SVN Userid"
b) I don't know if the SVN system has a web browser interface like the CVS system did.
http://svn.boost.org/trac/boost/browser
c) It seems to me that information regarding SVN access and boost customs and practices for using it to best advantage should be available form the main boost web page. Oh now I found it - its via a link titled Sandbox SVN. So I guess what I'm ask is for the main page to be tweaked so it's location is more obvious.
Patches welcome
d) The same goes for Trac. There is a link referring to it as a list of bug fixes. But it seems that its also intended to be used for reporting bugs. I don't think that's at all clear from the main page.
ditto
e) Poking around with the browser shows me a branch for RC_1_34_0. It seems we're releasing 1.34.1 - where is the branch for the actual code released? or are they the same? or?
http://svn.boost.org/trac/boost/browser/tags/Version_1_34_1 -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
David Abrahams wrote:
c) It seems to me that information regarding SVN access and boost customs and practices for using it to best advantage should be available form the main boost web page. Oh now I found it - its via a link titled Sandbox SVN. So I guess what I'm ask is for the main page to be tweaked so it's location is more obvious.
Patches welcome
OK - how would I go about doing that? check a change to the web site page on the trunk? I presume that woudn't migrate to the website until the next release. Or does "submitting a patch" mean something different?
e) Poking around with the browser shows me a branch for RC_1_34_0. It seems we're releasing 1.34.1 - where is the branch for the actual code released? or are they the same? or?
OK - that's just fine - but when I tried to create a branch off RC_1_34_0 I got an error. Is the error to advise me I should have been using Verson 1.34.1 rather than RC_1_34_0 or some other reason. Error: MKACTIVITY of '/svn/boost/!svn/act/7ac0dbeb-4f6d-0141-941c-1e06228e3d67': 403 Forbidden (http://svn.boost.org) Which I presume means I'm doing something unauthorized but it doesn't say what exactly. I searched through the SVN documentation for information about making Tags "readonly" to prevent someone accidently committing a change to a tagged version. I didn't find it but it seems that this functionality would be necessary. I'm still perusing the details. My intention is to create a branch off the latest release, check in and test my changes on this branch, and then merge them into the "trunk". If there's anything wrong with this procedure please let me know. Robert Ramey
Robert Ramey <ramey <at> rrsd.com> writes:
David Abrahams wrote:
c) It seems to me that information regarding SVN access and boost customs and practices for using it to best advantage should be available form the main boost web page. Oh now I found it - its via a link titled Sandbox SVN. So I guess what I'm ask is for the main page to be tweaked so it's location is more obvious.
Patches welcome
OK - how would I go about doing that? check a change to the web site page on the trunk? I presume that woudn't migrate to the website until the next release. Or does "submitting a patch" mean something different?
It normally means post a patch (you know, a unified diff) in a Trac ticket and assign it to the maintainer. However, there's no Boost website maintainer, and since you have commit privileges, unless you really think your change is controversial you should just follow the usual procedure: http://www.boost.org/more/updating_the_website.html
OK - that's just fine - but when I tried to create a branch off RC_1_34_0 I got an error. Is the error to advise me I should have been using Verson 1.34.1 rather than RC_1_34_0 or some other reason.
Error: MKACTIVITY of '/svn/boost/!svn/act/7ac0dbeb-4f6d-0141-941c-1e06228e3d67': 403 Forbidden (http://svn.boost.org)
Which I presume means I'm doing something unauthorized but it doesn't say what exactly.
I don't know what it is; if I were you I'd google for the error message.
I searched through the SVN documentation for information about making Tags "readonly" to prevent someone accidently committing a change to a tagged version. I didn't find it but it seems that this functionality would be necessary. I'm still perusing the details.
I wouldn't waste time on that, as you don't have permission to change the permissions on the Boost SVN.
My intention is to create a branch off the latest release, check in and test my changes on this branch, and then merge them into the "trunk". If there's anything wrong with this procedure please let me know.
nothing wrong with it AFAICT.
David Abrahams wrote: .
I searched through the SVN documentation for information about making Tags "readonly" to prevent someone accidently committing a change to a tagged version. I didn't find it but it seems that this functionality would be necessary. I'm still perusing the details.
see: http://svn.haxx.se/users/archive-2004-04/0178.shtml I believe most people use the 2nd option (a pre-commit hook script)
David Abrahams wrote:
Robert Ramey <ramey <at> rrsd.com> writes:
OK - that's just fine - but when I tried to create a branch off RC_1_34_0 I got an error. Is the error to advise me I should have been using Verson 1.34.1 rather than RC_1_34_0 or some other reason.
Error: MKACTIVITY of '/svn/boost/!svn/act/7ac0dbeb-4f6d-0141-941c-1e06228e3d67': 403 Forbidden (http://svn.boost.org)
Which I presume means I'm doing something unauthorized but it doesn't say what exactly.
I don't know what it is; if I were you I'd google for the error message.
Which only says that the server refused the address. I would guess that I'm not authorized to make such a request. I tried again and got the same response. So I guess we'll just leave it pending until Doug (who I believe is handling these kinds of issues) can address it.
I searched through the SVN documentation for information about making Tags "readonly" to prevent someone accidently committing a change to a tagged version. I didn't find it but it seems that this functionality would be necessary. I'm still perusing the details.
I wouldn't waste time on that, as you don't have permission to change the permissions on the Boost SVN.
Thank goodness for that. Actually, I suspect that marking that tag as "locked" would address my concern. The only reason I mention it is that I did it by accident with CVS. That is I checked out the the release branch and forgot it was the release branch and checked some changes. Just a suggestion - that's all.
My intention is to create a branch off the latest release, check in and test my changes on this branch, and then merge them into the "trunk". If there's anything wrong with this procedure please let me know.
nothing wrong with it AFAICT.
good to know Robert Ramey
on Sun Aug 12 2007, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
David Abrahams wrote:
Robert Ramey <ramey <at> rrsd.com> writes:
OK - that's just fine - but when I tried to create a branch off RC_1_34_0 I got an error. Is the error to advise me I should have been using Verson 1.34.1 rather than RC_1_34_0 or some other reason.
Error: MKACTIVITY of '/svn/boost/!svn/act/7ac0dbeb-4f6d-0141-941c-1e06228e3d67': 403 Forbidden (http://svn.boost.org) ^^^^
Which I presume means I'm doing something unauthorized but it doesn't say what exactly.
I don't know what it is; if I were you I'd google for the error message.
Which only says that the server refused the address. I would guess that I'm not authorized to make such a request. I tried again and got the same response. So I guess we'll just leave it pending until Doug (who I believe is handling these kinds of issues) can address it.
Did you notice that the http:// address for the repository is read-only? If you want to write you need to use https://. If you're working with a checkout from the http:// address use the "svn switch --relocate" command to update your working copy's repo address. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
Robert Ramey <ramey <at> rrsd.com> writes: [...]
f) Poking around a little more, I see:
root/branches/SPIRIT_1_6/boost/boost ... // all the boost headers
which is what I expect to see. I presume that all these headers are the state at the time the branch was made plus any merged in updates. OK
then I look at:
root/branches/SPIRIT_1_6/boost/libs ...// only find the directory for spirit
which kind of surprises me. I expect to see the whole set of libraries even though I know they havn't changed on this branch. I'm sure all the boost libraries haven't changed on this branch yet they are all there. What am I missing here?
The SPIRIT_... branches are really specific to Spirit development and release as a separate package. I don't remember how up to date the SPIRIT_1_6 branch is; you can find the state of the art, as far as Spirit 1.6 is concerned, under tags/SPIRIT_1_6_4 . Cheers, Nicola Musatti
participants (4)
-
David Abrahams -
eg -
Nicola Musatti -
Robert Ramey