Create github releases about projectscaffold HOT 16 OPEN

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.

from projectscaffold.

I thought the idea was to provide a opionated way to build (F#) projects?!

from projectscaffold.

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

from projectscaffold.

Ok regarding github.com releases:

• it's always available (at least compared to nuget.org which goes down regularly)
• you can download by clicking on website or using simple https client

from projectscaffold.

Okay. I've thought about it some more...
:-)
Let's do it. Having releases will avoid confusion in case the scaffold "changes opinions".

Of course, I won't really have time for this until next week.

from projectscaffold.

After reading your reply. I don't want releases for the scaffolding
project. I want to scaffold code which allows the generated projects to
push to github releases.
On Sep 19, 2014 5:55 PM, "Paulmichael Blasucci" [email protected]
wrote:

Okay. I've thought about it some more...
:-)
Let's do it. Having releases will avoid confusion in case the scaffold
"changes opinions".

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

from projectscaffold.

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.

from projectscaffold.

Let's see how it works in Paket and then I will send a PR. Just wanted to
discuss this idea.

2014-09-19 18:02 GMT+02:00 Paulmichael Blasucci [email protected]:

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.

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

from projectscaffold.

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.)

from projectscaffold.

will do.
At the moment I try to dogfood it in Github's octokit.

2014-09-19 18:37 GMT+02:00 Don Syme [email protected]:

Hi @forki https://github.com/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.)

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

from projectscaffold.

actually after thinking about it I'm not sure if libs should go to github releases.
Maybe it's more for apps. Still thinking about it.

from projectscaffold.

In some of my projects (F# Formatting, RProvider?, Deedle?) we actually push release binaries to release branch so that the binaries can be easily downloaded somewhere (which is indeed totally wrong). If GitHub releases provide an easy to use replacement for this then I really like the idea!

If I can get a free PR from @forki for F# formatting, that would be awesome :-)

from projectscaffold.

from projectscaffold.

let's start with fsprojects/FSharp.Formatting#197

afterwards I will add github releases

from projectscaffold.

@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.

from projectscaffold.

lol.

Maybe after we get
fsprojects-archive/zzarchive-VisualFSharpPowerTools#713 working ;-)

2014-09-20 12:40 GMT+02:00 Anh-Dung Phan [email protected]:

@forki https://github.com/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.

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

from projectscaffold.