After a discussion with the developers we've decided to no longer include the changelog in the packages. The file is currently half a meg and will only continue to grow. We suspect that the majority of our users don't read the changelog and we'd like to save them the effort of uploading it to their server if they can't upload the entire package.
Now we know some of you do like to read the changelog and the changelog is still important to us so we'll be making it available as a seperate download.
This change will happen in all future packages but previous packages will not be modified.
perhaps as a page on the site might be a way to handle it best? I dunno
But that sounds like a good idea, i never realized it was so large (i am used to reading the changelog from SVN, though, to be perfectly fair)
I was actually thinking about this yesterday when I downloaded 2.0
I never upload the changelog. I only upload index.php, SSI.php, Sources and Themes/default.
I am glad for the change though, its a waste of space that very few people even read.
Just incase it wasn't clear enough: the changelog will be available as a link from the download page.
Yeah I can't see a reason to include it in the zip file.
Is it linked in the admin area? That would suffice.
No need to link it in the admin area IMO.
I've always liked the idea of the changelog being in the zip. But I don't object to having it as a separate thing either. I can always look at SVN. :P
I think this is a good idea. A download at the web site would be best.
Quote from: christicehurst on January 04, 2008, 11:51:55 PM
I think this is a good idea. A download at the web site would be best.
Yeah smart idea too.
Although I've greatly enjoyed following the development through changelogs from beta/CVS releases I don't have access to, I think this is a very wise move. Now you just need to drop some of those old themes from the package as well ;) Only the previous default theme is needed to create continuity between new and old, and I'm sure no one would complain if the Babylon and Classic YaBB SE themes were available on the Theme Site instead of coming shipped with the installation package...
Good idea. Me too, didn't realize that it occupies that much space.
Yeah I wouldn't mind Classic theme being killed off.
No offense to the author, but compared to todays quality themes, it looks like a Baboons ass.
Personally I prefair classic over the rest, my own theme is based off it in fact.
Quote from: Sverre on January 08, 2008, 07:03:46 AM
Although I've greatly enjoyed following the development through changelogs from beta/CVS releases I don't have access to, I think this is a very wise move. Now you just need to drop some of those old themes from the package as well ;) Only the previous default theme is needed to create continuity between new and old, and I'm sure no one would complain if the Babylon and Classic YaBB SE themes were available on the Theme Site instead of coming shipped with the installation package...
That has been up for discussion before. And it's something I'd support.
Quote from: Gazmanafc on January 08, 2008, 04:28:09 PM
Quote from: Sverre on January 08, 2008, 07:03:46 AM
Although I've greatly enjoyed following the development through changelogs from beta/CVS releases I don't have access to, I think this is a very wise move. Now you just need to drop some of those old themes from the package as well ;) Only the previous default theme is needed to create continuity between new and old, and I'm sure no one would complain if the Babylon and Classic YaBB SE themes were available on the Theme Site instead of coming shipped with the installation package...
That has been up for discussion before. And it's something I'd support.
I have to agree here. I think having the default come with it and then the others as themes for download would be great.
Quote from: Ben_S on January 08, 2008, 04:04:29 PM
Personally I prefer classic over the rest, my own theme is based off it in fact.
Same here.