-
Notifications
You must be signed in to change notification settings - Fork 154
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
Create github releases #82
Comments
Hmm... I'm torn. Part of me likes the idea; I think it'd simplify certain use cases. But part of me never intended for the scaffold to require versioning. It was intended to be a learning tool (as much as it is a timesaver) for folks. So I guess I could see it argues either way. |
I thought the idea was to provide a opionated way to build (F#) projects?! |
I agree with @forki that the project has now really become "the opinionated template for F# community projects". Not sure you intended that @pblasucci but it's a great thing :) I'm not sure about GitHub releases, was looking at it but need to dig more |
Ok regarding github.com releases:
|
Okay. I've thought about it some more... Of course, I won't really have time for this until next week. |
After reading your reply. I don't want releases for the scaffolding
|
Whoops! I totally misunderstood your comment. Sorry... I'm trying to juggle too many things at once. Now that I understand what you meant, I think it's fine to have multiple deployment targets (nuget, github, etc). Let's just make sure the number of choices stays manageable and is explained clearly in the docs. |
Let's see how it works in Paket and then I will send a PR. Just wanted to 2014-09-19 18:02 GMT+02:00 Paulmichael Blasucci notifications@github.com:
|
Hi @forki, could you add the "GitHub releases" to the most important F# community projects first, e.g. FSharp.Data and FSharp.Compiler.Service and maybe a few others? Just so we get a feel for what it means and start to spread it through the community, (I assume nuget package releases will still be used as well.) |
will do. 2014-09-19 18:37 GMT+02:00 Don Syme notifications@github.com:
|
actually after thinking about it I'm not sure if libs should go to github releases. |
In some of my projects (F# Formatting, RProvider?, Deedle?) we actually push release binaries to If I can get a free PR from @forki for F# formatting, that would be awesome :-) |
let's start with fsprojects/FSharp.Formatting#197 afterwards I will add github releases |
@forki Would you mind to send a PR adding GitHub releases to VFPT :-)? Whenever we update a new version to VS Gallery, the old binaries disappeared. It's great to be able to use GitHub releases for archiving old binaries. |
lol. Maybe after we get 2014-09-20 12:40 GMT+02:00 Anh-Dung Phan notifications@github.com:
|
See fsprojects/Paket@68704bc and fsprojects/Paket@d33887d#diff-6074983490330a0aac1bd23c958232d7R282
It would not be that hard. If we want to do it.
The text was updated successfully, but these errors were encountered: