The glusterfs package includes a 6M ChangeLog file that dwarfs the rest of the package. I would suggest to trim this to a reasonable size.
fixed in 3.4.0betaX and in the forthcoming 3.3.2.
I see that instead of the 6M ChangeLog, glusterfs now ships a 1M compressed ChangeLog.bz2. This actually makes it hurt even more than shipping an uncompressed 6M ChangeLog: The iso media and rpm use xz compression, but when a file is already bz2 compressed, xz doesn't manage to compress it any further. Would it be possible to just drop the ChangeLog.bz2, or trim it like mclasen suggests?
Maybe we should just put the url to the git log in there?
Sure, sounds good to me.
The plan is to trim the ChangeLog to the most recent 50 lines and include a link to a git-tag'd commit log like https://forge.gluster.org/glusterfs-core/glusterfs/commits/v3.4.0beta3