[Release] 0.2.2 #55

New Issue

2016-01-05T18:40:01-05:00

darylteo commented

2016-01-05 18:40:01 -05:00

(Migrated from github.com)

Hey @MoOx never done this before (npm/bower wise).

Can you tell me how to go about it? Do I just up the version numbers in package.json/bower.json and push a release tag or do I need to do other things?

I think now that the main library is "functional" we should push it out as is and then deal with issues as they come up.

Hey @MoOx never done this before (npm/bower wise). Can you tell me how to go about it? Do I just up the version numbers in package.json/bower.json and push a release tag or do I need to do other things? I think now that the main library is "functional" we should push it out as is and then deal with issues as they come up.

MoOx commented

2016-01-06 01:31:16 -05:00

(Migrated from github.com)

Sure. I still have some questions for you:

Do you use bower? Cause since bower is kind of dead this days, I was thinking about removing it from there.
Is commonjs style lib enough for you? I was thinking about dropping the standalone build step (which is not very useful this days).
let me automate the process for publising. I like to have a command that run tests, create tag, publish on npm and update releases notes based on the CHANGELOG (so watcher receive a notification with the releases notes).

Sure. I still have some questions for you: - Do you use bower? Cause since bower is kind of dead this days, I was thinking about removing it from there. - Is commonjs style lib enough for you? I was thinking about dropping the standalone build step (which is not very useful this days). - let me automate the process for publising. I like to have a command that run tests, create tag, publish on npm and update releases notes based on the CHANGELOG (so watcher receive a notification with the releases notes).

darylteo commented

2016-01-06 02:45:58 -05:00

(Migrated from github.com)

From the perspective of legacy maintenance

would still support bower if it is not too much hassle. Lots of legacy projects (i.e. anything built before 2016 ;)) is likely to still need bower for front-end dependency management
standalone might also still be needed (like through CDNs). I might suggest putting the artifact in a more ecosystem friendly location (/dist)
sure please do. I am pulling from my fork for work purposes currently anyway.

From the perspective of legacy maintenance - would still support bower if it is not too much hassle. Lots of legacy projects (i.e. anything built before 2016 ;)) is likely to still need bower for front-end dependency management - standalone might also still be needed (like through CDNs). I might suggest putting the artifact in a more ecosystem friendly location (/dist) - sure please do. I am pulling from my fork for work purposes currently anyway.

MoOx commented

2016-01-11 02:22:08 -05:00

(Migrated from github.com)

Will handle that when I came back from a conference next week.

MoOx commented

2016-01-11 02:22:55 -05:00

(Migrated from github.com)

Btw, do YOU use bower?
standalone are legacy to me (and btw, https://npmcdn.com/)

- Btw, do YOU use bower? - standalone are legacy to me (and btw, https://npmcdn.com/)

darylteo commented

2016-01-11 02:35:05 -05:00

(Migrated from github.com)

Nope. Webpack npm for me (this year at least, who knows what more the js
community will come up with again by next year sigh)

But I am using it in at least one client legacy project right now at least.
On Mon, Jan 11, 2016 at 6:22 PM Maxime Thirouin notifications@github.com
wrote:

Btw, do YOU use bower?

standalone are legacy to me (and btw, https://npmcdn.com/)

—
Reply to this email directly or view it on GitHub
https://github.com/MoOx/pjax/issues/55#issuecomment-170452208.

Nope. Webpack npm for me (this year at least, who knows what more the js community will come up with again by next year _sigh_) But I am using it in at least one client legacy project right now at least. On Mon, Jan 11, 2016 at 6:22 PM Maxime Thirouin notifications@github.com wrote: > - Btw, do YOU use bower? > - standalone are legacy to me (and btw, https://npmcdn.com/) > > — > Reply to this email directly or view it on GitHub > https://github.com/MoOx/pjax/issues/55#issuecomment-170452208.

MoOx commented

2016-03-12 01:45:09 -05:00

(Migrated from github.com)

Sorry for the delay!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: iLoveElysia/pjax#55