Next Release - and Documentation release ?

[Geert Janssens]

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:
https://bugzilla.gnome.org/show_bug.cgi?id=652350

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 ?

Geert