Remove everything that's not AsyncSeq about fsharp.control.asyncseq HOT 9 CLOSED

I will have a look at this later today - want it in a dev branch for now?

from fsharp.control.asyncseq.

• the stuff that can't be removed should be internalized.
• try to get everything into one file so that we can use paket to link the file

from fsharp.control.asyncseq.

@CarstenKoenig - I jumped in and did most of this in #4, please take a look, thanks

from fsharp.control.asyncseq.

yes this should fix both - thank you.

As we are at it - what workflow do you prefer here: fork the repo and bring in pull-requests? Working on branches and merging those? Who is the one responsible for the main branch and/or release branches?

Sorry if there is a document somewhere explaining all this - just point me to it please ;)

Thanks

from fsharp.control.asyncseq.

in many other ProjectScaffold like projects we release basically everything that's merged to master (as soon as possible). The process is described at http://fsprojects.github.io/ProjectScaffold/release-process.html - but someone has to maintain the release-notes file and decide the version

from fsharp.control.asyncseq.

Fork + pull requests. In this case I self-committed to get us to the right baseline quickly

from fsharp.control.asyncseq.

ok - thanks - cleaning up the tangling branch then

from fsharp.control.asyncseq.

I think anyone with admin rights to both this repo and the nuget package can push releases of packages + docs ("build Release")

from fsharp.control.asyncseq.

This is a good point. you should allow more people to push to https://www.nuget.org/packages/FSharp.Control.AsyncSeq ;-)

from fsharp.control.asyncseq.