gemspec commits to master branch instead of current branch

[treeder]

No description provided.

[technicalpickles]

Sure, that seems fine. Just curious, but what branch do you develop/release from?

[treeder]

Usually master, but we have a beta branch that we're releasing beta's from. Also, the same issue would occur if you were doing bug fixes on a previous release.

[sarahmei]

+1. We have an internal gem that we are maintaining for 1.8.6 and 1.8.7 on separate branches.

[mxgrn]

+1.
I have a couple of extra branches where development of previous versions is taking place. Thus, after releasing the version, say, 0.7.1, that would be in 'master', I may need to switch to the '0-6' branch and release the version, say, 0.6.5.

(In short, a story similar to sarahmei's)

[technicalpickles]

I'm cool with this as a feature. We've had to do a similar thing when doing preleases of a gem.

I haven't had a ton of time to make it happen though. If someone were to send a pull request before my next jeweler hack session, I'd be happy to review and see about getting it merged.

[grosser]

#207

[treeder]

@technicalpickles could you please merge that pull request to fix this?

[technicalpickles]

I've been pretty swamped recently, so haven't had much time for some TLC of jeweler. I will get it out as soon as I can.

A quick pass of the pull request looks good though.

On Sep 28, 2011, at 6:15 PM, Travis Reeder wrote:

@technicalpickles could you please merge that pull request to fix this?

Reply to this email directly or view it on GitHub:
#194 (comment)

[treeder]

Any word on this?

[railsformers]

We need this feature too. Some progress in merging pull request?