On Thu, Oct 06, 2005 at 11:27:54AM -0400, Chris Shoemaker wrote: > On Thu, Oct 06, 2005 at 10:51:45AM -0400, Derek Atkins wrote: > > Quoting Chris Shoemaker <[EMAIL PROTECTED]>: > > > > >>Granted, we could probably write a script that makes the necessary > > >>modifications, commits the changes, tags the release, and runs > > >>./autogen.sh ; make distcheck > > > > > >Yeah, release number increments are easy to automate. And I think the > > >typical alpha tester would be satisfied with a verbatim selection of > > >the ChangeLog since last release. > > > > Well, want to spend a little time to write the script that does all this? > > Honestly, not really. I'm not familiar with the release process. > But, if no one else will, then I guess I can take a whack. > > Can we outline the process? > > * clean cvs co > * change GNUCASH_MICRO_VERSION in configure.in > * ./autogen.sh && make distcheck > * post tgz to website
Question about the tarball. Are end users supposed to install with './autogen.sh' or './configure'? I was hoping that maybe the tarball could be installed using configure instead of autogen.sh, but it seems maybe not. If the end users are supposed to use autogen.sh shouldn't there be instructions like that somewhere, say INSTALL? -chris > * post new ChangeLog entries to website > * cvs commit > * cvs tag > > what else? > > -chris > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
