Skip to content

Conversation

@mamsterla
Copy link

No description provided.

@frapontillo
Copy link
Owner

I'll accept it if you use ~1.4.8, which is the latest one.

@mamsterla
Copy link
Author

I use 1.4.8, but it should work for all 1.4.x branches - folks who are on large projects can’t always switch quickly. Thanks.

-MA

On Nov 26, 2015, at 12:05 AM, Francesco Pontillo notifications@github.com wrote:

I'll accept it if you use ~1.4.8, which is the latest one.


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

@frapontillo
Copy link
Owner

Yeah, I know, but it's common practice to specify ~1.4.8 in the dependencies, that'll pick up all next patch releases.

@mamsterla
Copy link
Author

What about all the people on 1.4.3 or 1.4.5? Your code still works with it. No reason to force upgrade folks just for the gauge.

-MA

On Nov 26, 2015, at 12:37 PM, Francesco Pontillo notifications@github.com wrote:

Yeah, I know, but it's common practice to specify ~1.4.8 in the dependencies, that'll pick up all next patch releases.


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

@frapontillo
Copy link
Owner

They will not be forcefully updated. If they specify a lower version of angular bower will honor that and ask for a specific resolution, if none is provided.
Specifying a higher release number forces the CI to run tests on the latest version (which I care about more than older ones, TBH) and the maintainer to fix issues if any arise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants