New release

[nfantone]

We should merge and publish all these new features, releasing as 0.2.0 to npm.

@disintegrator Could you, please, also:

• Make develop the default branch. If you clone the repo, let's assume you want to collaborate and push some code. If you fork, it should also be from that branch.
• Protect master branch.
• Create a named tag for the 0.2.0 release before publishing to npm.
• Take a look at the general Seneca repository guidelines and see if you can setup this repository to comply to them.

Thanks!

[disintegrator]

@nfantone set the default branch to develop and set master to protected

[disintegrator]

@nfantone skimming through the guidelines, I don't see anything that we are falling short on besides tagging of npm releases

[nfantone]

Well... What about labels for issues? If I recall correctly, ours don't
exactly match with the ones proposed by the guide.
On Jan 31, 2016 7:55 PM, "George Haidar" notifications@github.com wrote:

@nfantone https://github.com/nfantone skimming through the guidelines,
I don't see anything that we are falling short on besides tagging of npm
releases

—
Reply to this email directly or view it on GitHub
#10 (comment)
.

[disintegrator]

I just checked the issues and so far we use bug, question and request (I just added it). These are all listed on the guideline page. I have also tagged the closed issues with the most appropriate labels I can pick.

[nfantone]

I'd like to have the "discussion" label. #6, for instance, could be labeled as such. What do you think?

[nfantone]

set the default branch to develop and set master to protected

Thank you very much for that.

[disintegrator]

Added discussion label to #6

[nfantone]

👍 Great

[nfantone]

@disintegrator Many more features added, including multi-pin support, custom queue naming and pre-commit hooks for lint validations.

[disintegrator]

Amazing work @nfantone.
As an aside: When I have a sec, I'll move this project to an organisation to make sure you are getting recognised for your contributions.

[disintegrator]

If you don't have permission to merge this PR, let me know when you'd like me to do it

[nfantone]

@disintegrator I do have permission. But it's your project, really. And, besides, I'd like someone to, at least, do a sanity check on all the crap I'm pushing.

What I wouldn't be able to do is publish to npm. So, there's that.

Apart from those things, you can merge this PR whenever you want.

[nfantone]

I'll move this project to an organisation to make sure you are getting recognised for your contributions.

Thanks, man. You don't really need to, though. Seriously.

[cicavey]

Any movement here? My team is really excited to use these changes, but would very prefer a public release to npm over a development snapshot. Is there anything I/We can do to help?

[nfantone]

@cicavey Merged. @disintegrator will need to push this to npm, though. Sorry for the lack of response.

[cicavey]

Wow. Didn't expect that kind of turnaround. Thanks!

[nfantone]

@cicavey Released to npm under 0.2.0 tag.

https://www.npmjs.com/package/seneca-amqp-transport