Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release date [!important] #3800

Closed
djleonskennedy opened this issue Mar 27, 2017 · 18 comments
Closed

release date [!important] #3800

djleonskennedy opened this issue Mar 27, 2017 · 18 comments

Comments

@djleonskennedy
Copy link

Hello

Please provide an approximate release date for new version of BETA, very need several fixes that were merged

Thank you

@fxck
Copy link
Contributor

fxck commented Mar 27, 2017

Use https://github.com/angular/material2-builds if you want snapshot of master.

@djleonskennedy
Copy link
Author

@fxck Could you clarify how to use it ?

@fxck
Copy link
Contributor

fxck commented Mar 27, 2017

@djleonskennedy
Copy link
Author

@fxck understood, thank you

@sasxa
Copy link

sasxa commented Mar 27, 2017

@fxck I was getting this error with material2-builds.git#b74e662528934950652d64fc41ca7ec2a852cf2b:

ERROR in ./~/css-loader?{"sourceMap":false,"importLoaders":1}!./~/postcss-loader!./~/sass-loader!./src/styles/theme.scss
Module build failed:
@import '~@angular/material/core/theming/all-theme';
^
      File to import not found or unreadable: ~@angular/material/core/theming/all-theme.

Looks like something changed with how custom themes work. Just to confirm, now we need to import:

@import '~@angular/material/theming';

instead of

@import '~@angular/material/core/theming/all-theme'

Correct?

@leo6104
Copy link

leo6104 commented Mar 27, 2017

@sasxa Yes. I did custom theme by that way and there was no problem.

@fxck
Copy link
Contributor

fxck commented Mar 27, 2017

That's because the paths were recently changed (couple of issues were already opened about it, search them), that's the price you have to pay for using cutting edge releases, you have to fish commits for breaking changes.

@sasxa
Copy link

sasxa commented Mar 27, 2017

@fxck @laco0416 OK, thanks. It's a really small change and not a big issue, just wanted to confirm. :-)

@mmrath
Copy link

mmrath commented Mar 28, 2017

I am eager to use the snapshot builds but my build server is behind firewall with access only to internal npm registry which can download from npm registry. So the build server can't use snapshots from github. It would be great if a periodic snapshots can be published to npm may be with experimental tag.

@kamarouski
Copy link
Contributor

Still curious what is the roadmap for next releases? Are we going to see new beta version any time soon?

This is just to feed my curiosity :)

@djleonskennedy
Copy link
Author

@kamarouski you're happy if just "curiosity", i looking forward new release as the second coming of Christ

@djleonskennedy
Copy link
Author

@mmrath totally agree

@kamarouski
Copy link
Contributor

@djleonskennedy haha. If you want to get latest fixes there is an option to get latest master version. This makes life a bit easier.

I'm waiting for a few extra components like data table and calendar, though when I started using beta version of Angular Material I accepted the fact that there is no fixed schedule, there can be breaking changes and some parts are missing.

@Cleudi
Copy link

Cleudi commented Mar 28, 2017

Not everybody has the option to use snapshots... therefore kind of a release schedule would really be helpful.

We also use material.... we decided to use it 9 months ago, assuming that there will be at least something like a stable version until our product is entering productive mode... assumption was wrong, and we can not risk breaking features because of a snapshot update...

@fxck
Copy link
Contributor

fxck commented Mar 28, 2017

read #3799 (comment)

@mmrath
Copy link

mmrath commented Mar 28, 2017

@fxck does not really help. I know it is in beta and it will be unstable. but why not release few frequent unstable betas or even experimental or nightly build

@jelbourn
Copy link
Member

We're trying to release a new beta soon but are still working on smoothing out a particular issue with Webpack + tree-shaking for the components.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants