Bowerify

[peyerluk]

• Add bower configuration
• Add release grunt task

[peyerluk]

@matteoagosti I plan to use bower to load editable into the engine and also into the editor. So I added a bower configuration and a release task to add git version tags. The versioning is still under discussion in upfrontIO/guides#3 but I started implementing preliminary stuff so we can get a better feeling for it.

Do you like it this way? Other suggestions? Mergeable?

[matteoagosti]

Bower makes perfectly sense for integration in the editor and the engine. So it's a go for me.
With regards to the grunt task for the release, have you been checking https://github.com/cburgdorf/grunt-release-branch ?

[peyerluk]

Do you know if bower or npm can work with release branches?

[matteoagosti]

Yes, with bower you just append the # to the package name, followed by the release name or the sha of the commit.

With npm you can do it for sure, by specifying the full path to the release branch. With just the package name you can specify the tag using the @ if I'm not mistaken (can't check, on the train now :p)

Il giorno 26-gen-2014, alle ore 13:26, Lukas Peyer notifications@github.com ha scritto:

Do you know if bower or npm can work with release branches?

—
Reply to this email directly or view it on GitHub.

[peyerluk]

I guess you can do the same with npm. After all bower tries to copy the interface of npm as far as I know. What is the big advantage of a separate release branch?