Next Release - and Documentation release ?
jralls at ceridwen.us
Fri Jul 1 11:57:53 EDT 2011
On Jun 28, 2011, at 12:50 AM, Geert Janssens wrote:
> On maandag 27 juni 2011, John Ralls wrote:
> > Yup, false alarm, I forgot to run make distcheck to clear out the swig
> > files so I had business-core.c from trunk which imported a symbol that
> > isn't in 2.4. Everything passes now, and the fix for 653056 is checked in.
> > If no one else has anything else that needs to go into 2.4.7, Christian
> > can update configure.ac and tag it.
> > Regards,
> > John Ralls
> I have nothing more to add to the code before 2.4.7.
> However, I'd like to point at a documentation bug that may impact this release:
> Cristian Marchi, our currently most active documentation developer, has asked to release the documentation together with the new release. There are many changes in the documentation that never were released so far.
> I know the documentation release is independent of the program in principle, but both the Windows and the OS X build include it by default. And all linux distributions create a separate package for the documentation. In that view it would indeed be good to release the documentation as well.
> I know how to tag a release, create a tarball and set up the new release on our website. But I don't know or don't have permission for the other steps:
> - how to upload the tarball to Sourceforge ?
> - how about a news item ? Is there some template to reuse, or should we create a new one ? Anyone volunteering ?
Are we waiting on something to do this release (or releases, if all the doc changes are in svn and ready for release)?
Geert, you're an admin on the sourceforge project, so while you already have release and shell access to upload to frs, even if you didn't you could fix it yourself. 652350 seems to be about setting up a formal release process. We can do that, but I don't think that's a prerequisite for releasing 2.4.7. See the Sourceforge docs on how to use the files page (or just go to it; they've made using it pretty obvious.)
I've got some errands to run, but if no one objects and no one else has done so, I'll update the version numbers, tag the versions, and make dist this afternoon. (Three changes, right? Gnucash itself 2.4.7, Gnucash-Docs 2.2.2, and Gnucash-Docs 2.4.1?)
More information about the gnucash-devel