Raise version 0.3.0 with a tag

[michaelschnyder]

Could you @xeronimus please add a tag to the current version?

[xeronimus]

https://github.com/hatchteam/twigs/tree/0.2.3

[michaelschnyder]

I'm puzzled: Isn't it 0.3.0 anymore because of breaking changes in the ui-angular lib?

https://github.com/hatchteam/twigs/pull/36/files

[xeronimus]

Last release was 0.2.2, right?

Michael Schnyder notifications@github.com schrieb am Mi., 10. Feb. 2016
21:37:

I'm puzzled: Isn't it 0.3.0 anymore because of breaking changes in the
ui-angular lib?

https://github.com/hatchteam/twigs/pull/36/files

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

[michaelschnyder]

Just saw this and talked to @ChristianKohler about the version, because he stated it would be a breaking change, and therefore the Minor was updated

[xeronimus]

the PR merge into master was my fault. should have gone to develop. thus the confusion.

where do you see the breaking changes in @ChristianKohler 's commit 79d8081 ?

hm. since the user of twigs has to include angular-bootstrap 1.x which has breaking changes ... ?

[michaelschnyder]

Okay, I see.

I and @ChristianKohler were both faced with changes in the underlying angular-boostrap ui library. They introduced a breaking change in there, so we both thought it would be a good idea to raise a major chainge in twigs, because the change in angular-boostrap not only changes the names of the services twigs is using, it also changes all names of directives and could even have impacts on your styles as long as they are made especially for the components which where renamed.

See: https://github.com/angular-ui/bootstrap/wiki/Migration-guide-for-prefixes

[xeronimus]

Thanks for elaborating. I understand.

is there another pressing issue I should include before raising to 0.3.0 ?
would you quickly comment on #39 ?

thanks & cheers