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

Next version? #522

Closed
ojmoreno opened this issue Jul 22, 2019 · 20 comments
Closed

Next version? #522

ojmoreno opened this issue Jul 22, 2019 · 20 comments
Labels

Comments

@ojmoreno
Copy link

Hello,
when is planned to release the next version on NuGet? 2.4.4 or 2.5.0 or 3.0.0 ?
Best regards

@mrbean-bremen
Copy link
Member

@tebjan - this is for you :)

@kiwiingenuity
Copy link

I'm working on a project that deploys .Net Core 3.0. Currently working with the v3.0.0-preview6 SDK.
I'm soon wanting to create SVG drawing from scratch.
What are the options available to me, to make the SVG.DLL work with my environment?

If the option is to create another branch, then Tebjan can you give me a hint as to what is involved?

@gvheertum
Copy link
Member

What are the options available to me, to make the SVG.DLL work with my environment?

If you download/clone this repository (or fork it to a local copy) you can compile the sources. The current master branch of the project is core 2.2 compatible, so if you perform a build targeted on donetcore you should get a DLL you can include in your project.

Just run the command below in the /Sources/ folder

dotnet build -c release -f netcoreapp2.2 Svg.csproj

this should put the dll you want in the bin/Release/netcoreapp2.2/ folder (or release if you build release)

@kiwiingenuity
Copy link

@gvheertum - I can confirm your solution works!
The other day I cloned the Master, did a Release build... the required DLL was in the core 2.2 folder.

@mrbean-bremen
Copy link
Member

@gvheertum - can you add an instruction for building the library to Q&A? As you already did an entry there ;)
Actually this is something that belongs to a "Getting started" page - what do think, shall we add a new Wiki page for the time being (in the long run, we may use GitHub pages for this)?

@gvheertum
Copy link
Member

gvheertum commented Jul 26, 2019 via email

@mrbean-bremen
Copy link
Member

Thanks! I'm planning to setup GitHub pages some time, just don't know when I'll get to it. I see the Wiki as a temporary place to collect some documentation. Any documentation is an improvement!

@gvheertum
Copy link
Member

Any documentation is an improvement!

I like the way you think ;)

@gvheertum
Copy link
Member

@mrbean-bremen, can you have a look at: https://github.com/vvvv/SVG/wiki/Getting-started

I think this might cover a large part of the getting started. Maybe we can update the Readme.md in the project with references to the Wiki and/or add/move parts of the wiki to the Readme.md. This might be helpful for people downloading the sources, since the readme.md will be included in the sources.

@mrbean-bremen
Copy link
Member

Very nice, I like that! A very comprehensive guide for starting to use the library - we should definitely point the Readme to it, and now we have a real starting point for future documentation 👍

@mrbean-bremen
Copy link
Member

I updated the Readme and the documentation issue with a link to the new page.

@tebjan
Copy link
Contributor

tebjan commented Jul 29, 2019

I'll publish a new preview. @mrbean-bremen if you think the current master is ready for an official release, i'd push an official release soon after.

@tebjan
Copy link
Contributor

tebjan commented Jul 29, 2019

@mrbean-bremen
Copy link
Member

I think an official release would be a good idea. If something pops up after the release, we (e.g. you :) can always make a dot release.

@gvheertum
Copy link
Member

I think an official release would be a good idea. If something pops up after the release, we (e.g. you :) can always make a dot release.

Agreed, since we move up a major version, I think it's clear to users that there might be compatibility issues. Perhaps for a while we could support the 2.0 versions for legacy purposes and have the 3.0 as current release.

I would expect some might experience/fear issues with the 3.0 since there were quite some changes with regard to the .NET Core migration, so some might prefer staying on the older versions.

@tebjan
Copy link
Contributor

tebjan commented Jul 30, 2019

Yes, sounds good. I'll publish the package today. Thanks for your hard work!

@mrbean-bremen
Copy link
Member

so some might prefer staying on the older versions.

That's always a possibility - judging by the issues quite a few users do not use the latest nuget version anyway. But having the possibility to use an "official" version that supports .NET is a nice feature.

@gvheertum
Copy link
Member

@tebjan Did you get around to publishing a non-pre-release version of the package? If I look at nuget.org I still see the 3.0 is still flagged as pre-release.

I also thought about adding a small part to the getting started regarding the versions 2 and 3, so I will update the documentation with a proposal.

@tebjan
Copy link
Contributor

tebjan commented Aug 26, 2019

Master branch looks good to me and so far no big issues. I'll publish a 3.0 package.

@tebjan
Copy link
Contributor

tebjan commented Aug 30, 2019

got it, now appveyor will also build the nuget package, including xml documentation: https://www.nuget.org/packages/Svg/

@tebjan tebjan closed this as completed Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants