Hi Noah, I just went through the bootstrap shell script and I think I can include the git part in the script. So basically how this would work would be like this right?: 1.User runs bootstrap 2.Bootstrap fetches the git commit messages too and stores in an rst file 3.The python script uses this rst file to generate documentation. Please do correct me if I've misunderstood something.
On Sun, Jul 28, 2013 at 2:47 PM, Noah Slater <nsla...@apache.org> wrote: > Yashin, > > I was just going through your proposal here: > > > https://cwiki.apache.org/confluence/display/COMDEV/Proposal+for+CouchDB+automated+release+process+documentation+-+Yashin+Mehaboobe > > It occurred to me that "make" is not the best place to put this stuff. > Anything that happens in make cannot assume the presence of Git. The only > place you can work with Git (or in fact make network requests) is from > ./bootstrap. Is this something you can accommodate? > > > On 22 July 2013 18:08, Yashin Mehaboobe <yashin...@gmail.com> wrote: > > > Hi, > > I've slightly modified the proposal according to Dirkjan's suggestions. > > I'll also concentrate more on getting viable information from the git > > rather than the build process. Thanks for the suggestions :) > > > > Thanks Noah, It's a pleasure to be working with you people :) > > I'll look through the threads you've suggested and I'm currently working > on > > a very naive implementation of the Git info grabber. Will keep all of you > > posted! :) > > > > > > On Sun, Jul 21, 2013 at 2:29 PM, Noah Slater <nsla...@apache.org> wrote: > > > > > This is very good to hear. Welcome aboard, Yashin. > > > > > > Please familiarise yourself with the previous threads we've had on this > > > topic: > > > > > > > > > > > > http://markmail.org/search/?q=list%3Aorg.apache.couchdb.dev+%22%5BVOTE%5D+Git+Commit+Messages%22+order%3Adate-forward > > > > > > > > > > > > http://markmail.org/search/?q=list%3Aorg.apache.couchdb.dev+%22%5BDISCUSS%5D+How+to+generate+our+release+notes%22+order%3Adate-forward > > > > > > > > > > > > http://markmail.org/search/?q=list%3Aorg.apache.couchdb.dev+%22%5BDISCUSS%5D+Git+workflow%22+order%3Adate-forward > > > > > > Note that we do not have community consensus around how we want to > > > generate our release notes. So one of the important parts of this work > > will > > > be regularly sharing your progress with the list, so that we can > discuss > > > things. > > > > > > I expect that if we adapt our Git workflow, we can probably get 80% of > > the > > > way there, and the other 20% will have to be done by a human each time. > > But > > > it would be good to see some concrete data! > > > > > > Very excited to see where you get with this. > > > > > > > > > > > > > > > On 20 July 2013 16:41, Dave Cottlehuber <d...@jsonified.com> wrote: > > > > > >> On 19 July 2013 16:29, Dirkjan Ochtman <dirk...@ochtman.nl> wrote: > > >> > On Thu, Jul 18, 2013 at 9:21 PM, Yashin Mehaboobe < > > yashin...@gmail.com> > > >> wrote: > > >> >> I've installed couchdb on a Linux VPS. I cloned the git repository > > and > > >> >> compiled it from source but I haven't created any databases yet. > I've > > >> looked > > >> >> through the /share/doc/src rst files as well as the sphinx conf.py > > >> file. How > > >> >> I plan on implementing this is to use the following to gather the > > >> changes. > > >> >> -The rst files from /share/doc > > >> >> -The git commit messages obtained using git-python > > >> > > >> +1 > > >> > > >> > I'd personally go with dulwich or pygit2 for this rather than > > >> > git-python, since they're implemented as native libraries rather > than > > >> > wrappers around shelling out to other processes. > > >> > > >> Let me know which one seems best & I'll confirm it can run on windows > > >> in our kludgy build chain, and at what version. > > >> > > >> A+ > > >> Dave > > >> > > > > > > > > > > > > -- > > > NS > > > > > > > > > > > -- > > - Yashin Mehaboobe > > > > > > -- > NS > -- - Yashin Mehaboobe
