TGZ broken

[David Latapie]

Hi,

First-time user, first-time poster.

The TGZ of the 0.9 misses most files. I was going to scratch blueprint
css altogether in favor of YAML, then my intuition led me to try out
the zip file, just in case.

So, either abandon dual compression or be sure to keep them in sync!

Bye

[Christian Montoya]

On Sun, Aug 9, 2009 at 12:47 PM, David Latapie<david....@gmail.com> wrote:
>
> Hi,
>
> First-time user, first-time poster.
>
> The TGZ of the 0.9 misses most files. I was going to scratch blueprint
> css altogether in favor of YAML, then my intuition led me to try out
> the zip file, just in case.

David,

Were you able to get all of the files by checking out the project? We
have no control over the compressed packages, they are automated.

--
--
Christian Montoya
mappdev.com :: christianmontoya.net

[David Latapie]

Hi Chris,

2009/8/10 Christian Montoya <sir...@gmail.com>:

>
> On Sun, Aug 9, 2009 at 12:47 PM, David Latapie<david....@gmail.com> wrote:
>>
>> Hi,
>>
>> First-time user, first-time poster.
>>
>> The TGZ of the 0.9 misses most files. I was going to scratch blueprint
>> css altogether in favor of YAML, then my intuition led me to try out
>> the zip file, just in case.
>
> David,
>
> Were you able to get all of the files by checking out the project? We
> have no control over the compressed packages, they are automated.

Yes, no problem with the zip file.

By the way, I am currently writing an article about how to meerge
WordPress, WordPress child themes, and Blueprint, as I believe this
would be a great starting point for non PHP-aware themers. I'll keep
you in touch.

--
</david_latapie>
david.latapie.name U+0F00
Proper Preparation Prevents Poor Performance
On ne fait qu’une seule première impression

[Thomas Koch]

> On Sun, Aug 9, 2009 at 12:47 PM, David Latapie<david....@gmail.com>
wrote:
> > Hi,
> >
> > First-time user, first-time poster.
> >
> > The TGZ of the 0.9 misses most files. I was going to scratch blueprint
> > css altogether in favor of YAML, then my intuition led me to try out
> > the zip file, just in case.
>
> David,
>
> Were you able to get all of the files by checking out the project? We
> have no control over the compressed packages, they are automated.

On http://www.blueprintcss.org/ you have put wrong links for the downloads.
The links you provide point to the most current commit in the master branch,
which means, users automatically download your current development version
instead of the stable version.

The correct links can be found at
http://github.com/joshuaclayton/blueprint-css/downloads
which resolves for 0.9 to

http://github.com/joshuaclayton/blueprint-css/tarball/v0.9
for the tarball and
http://github.com/joshuaclayton/blueprint-css/zipball/v0.9
for zip.

Best regards,

Thomas Koch, http://www.koch.ro

[David Latapie]

2009/8/10 David Latapie <david....@gmail.com>:

> By the way, I am currently writing an article about how to meerge
> WordPress, WordPress child themes, and Blueprint, as I believe this
> would be a great starting point for non PHP-aware themers. I'll keep
> you in touch.

Here’s the article:
<http://david.latapie.name/blog/3997-bluebox-child-skeleton-definitive-wordpress-starter-theme-so-far?lang=en>

[Thomas Koch]

> On Mon, Aug 10, 2009 at 9:11 AM, Thomas Koch<tho...@koch.ro> wrote:
> > On http://www.blueprintcss.org/ you have put wrong links for the
> > downloads. The links you provide point to the most current commit in the
> > master branch, which means, users automatically download your current
> > development version instead of the stable version.
> >
> > The correct links can be found at
> > http://github.com/joshuaclayton/blueprint-css/downloads
> > which resolves for 0.9 to
> >
> > http://github.com/joshuaclayton/blueprint-css/tarball/v0.9
> > for the tarball and
> > http://github.com/joshuaclayton/blueprint-css/zipball/v0.9
> > for zip.
>

> Whoa whoa whoa, hold your horses, pard'ner! The master branch IS the
> latest stable branch. There's no harm in downloading it. It also
> hasn't changed a lick since version 0.9.*
>
> * though I should probably make some improvements... eventually.

I think you're wrong. On blueprintcss you state, that the last update was made
on june 2 and that the current (stable) version of blueprint is v0.9. There's
a tag in the GIT repository with the name "v0.9" from mai 29. I assume that
you refer to this tag, when you speak about version v0.9.
When you follow the "all releases" link you'll also be presented a version
v0.9 which refers to the tag v0.9.

So one could safely assume, that what you download from the frontpage as the
most current stable should be the same as what you download when you follow
the all releases link and take the most resent release.

But what you get by downloading from the frontpage differs from v0.9 by 13
commits, the most recent from august 6 by eric clemmons.

I'm sure you did not intend to make 13 releases from june until now without
bumping the version number and keeping the release date on your frontpage
current, did you?