NuGet about knockback HOT 15 CLOSED

@Centuri: I'm totally happy to publish a NuGet package for Knockback. I've had one request before...the main problem is that I do not have VisualStudio and I believe it is needed for testing.

Would you like to create and maintain the Knockback NuGet package?

from knockback.

@kmalakoff: Sure, we'll create and maintain the package as long as we use it. We're currently evaluating different approaches for a greenfield rebuild of our software. Knockout, Knockback and Backbone is currently our primary canditate.

from knockback.

@kmalakoff: Ok, you're published: https://nuget.org/packages/Knockback.js

Ran into some dependecy issues so the package is published as version 0.12.2 since it won't allow you to update a published package.

from knockback.

@Centuri: excellent! Thank you so much for agreeing to set this up and to maintain it. If you decide to discontinue using Knockback, just let me know and we'll find another maintainer...

Two quick questions...

1. To update the version to be in sync with the latest numbering in Github, do I need to bump the Github branch and package version number?

2. If I do a new release of Knockback and bump the version number, how do I ensure the NuGet package is updated? Do I send you an email or is there a more modern approach?

Cheers!

from knockback.

@kmalakoff:

1. I don't see a reason to bump the version number on github unless you're planning another minor release (0.13). It would however be useful if you include the version number when naming the library e.g. Knockback.0.13.0.min.js

2. We have forked your repo on GitHub so I guess we'll be notified that way. But if you don't mind sending an e-mail that'd be great.

from knockback.

@Centuri : I was also wondering where you found the 0.12.2 version from (the current version is 0.14.2). I do not have an official release process, but just link to a live/static file in Github in the README with the latest version (which is why the file currently doesn't have the version number in it so the link is persistent) that I label and push after accumulating a certain number of well-tested changes in my local version.

It sounds like maybe I should start building the library in official releases, put them in Github's "downloads" so they can be linked to official releases with the version number appende in the filename.

I guess my concern with not having a live/static named version is having to maintain external links to the latest version, but I guess with NuGet and npm, I can start try to find a process that is maintainable to push new versions out.

To be certain of an update in NuGet, I'll send you an email when I do new minor or major releases. Thank you for agreeing to this!

from knockback.

@kmalakoff: I got the releasenumber from the "official" site. Since it wasn't present in the source or naming. Never occured to me to check the README file. I'll publish a new package on NuGet with the same content but correct version numbering.

cheers

from knockback.

@kmalakoff: Just noticed the version number is in the source lol, how did I miss that

from knockback.

@Centuri : thank you!

from knockback.

@century: no worries!

Would you be able to publish your repo for knockback on NuGet? (for
knockout, Steve Sanderson has created a repository like this:
https://github.com/SteveSanderson/knockout.nuget)

Cheers!

Kevin

from knockback.

@century: Knockback 0.15.0 is live! Can you please release it to NuGet?

Cheers,

Kevin

On Sat, May 5, 2012 at 1:23 PM, Kevin Malakoff [email protected] wrote:

@century: no worries!

Would you be able to publish your repo for knockback on NuGet? (for
knockout, Steve Sanderson has created a repository like this:
https://github.com/SteveSanderson/knockout.nuget)

Cheers!

Kevin

from knockback.

@century: I found a minimizing problem and had to quickly bump the version
to 0.15.1.

On Fri, May 11, 2012 at 12:07 AM, Kevin Malakoff [email protected]:

@century: Knockback 0.15.0 is live! Can you please release it to NuGet?

Cheers,

Kevin

On Sat, May 5, 2012 at 1:23 PM, Kevin Malakoff [email protected]:

@century: no worries!

Would you be able to publish your repo for knockback on NuGet? (for
knockout, Steve Sanderson has created a repository like this:
https://github.com/SteveSanderson/knockout.nuget)

Cheers!

Kevin

from knockback.

@kmalakoff: Hey Kevin, I've updated the NuGet package to 0.15.1 and added a new public repo for the package here: https://github.com/Centuri/knockback.nuget

from knockback.

Awesome dude.

from knockback.

Awesome! Thank you!

from knockback.