When will Nancy 2 be formally released? #2872
Comments
bluetentacle
changed the title
|
Hi, I have the same exact question. It's a bit scary to see that the whole project seems to have slowed down a lot, with this 2.0 pending release that doesn't have public pre/beta releases anymore. Is there anything that basic users could help with, without having to fully understand the internals of Nancyfx? Please take no offense, this is precisely because it's a great project that I/we express such questions and concerns. |
|
I would also like to know what the plans are. This is a great tool and if there is anything that can be done I'd like to know. |
You could sponsor some work through the Patreon? |
Done! |
|
Likewise, May i suggest adding the Patreon information on a more noticeable place (maybe the readme file)? Didn't found out until i read this thread. |
|
What is left to do in Nancy? I mean what's the point in donating money to a black hole? Last update was a couple months ago, but it appeared to be really minor. I just want a solid base to do web services with. I need the NetCore support of Nancy 2, but I don't need any view support. I just need something that works out of the box. Nancy has been answering the mail on that, but I wonder if I should just use Owin directly. |
|
This Issue had a checklist of what was needed before 2.0.0-d could be released. But it is now closed without all checks being ticked so no idea. Was actually wondering the same myself about the progress and what was left in the roadmap (to event see if I could contribute). |
|
We've pretty much baked what we want in 2.0.. I'm just looking for some personal time to get the release out the door. My hope is that we can make that happen this or the week after! |
|
Cool @thecodejunkie! Looking forward to it. Would that be version 2.0-d or a final 2.0 release?? |
|
Most likely final :D |
|
I think we can all agree that the 2.0 Release will not gonna happen. I have been looking at this framework for a while now and i guess its no longer actively developed. |
|
Any news? I am also thinking we will never have Nancy v2 released :-( |
|
Any update on Nancy 2.0? Last mention was "My hope is that we can make that happen this or the week after!" about two months ago... |
|
Hi Andreas, do you have any thoughts about wrapping up the Nancy 2.0 release? Is there anything that can be done to help? Best regards, Will |
|
I think at this point given the direction that aspnet core 2.x has taken which aligns to some of the reasons of why nancy was born there isn't probably much value in investing into this framework anymore. Specially at the rate that .net core is moving and given the fact that it is also open source. Perhaps it would be best to just archive this project so that people don't keep asking when v2 is going to be released? |
|
Well, there is people still using Nancy for already existing projects.. so I would favor releasing 2.0 and letting it clear there wont be a 3.0.. this way, the people who trusted the project wont be left alone in the dark. |
|
In fact, there are even people using Nancy for new projects. A formal 2.0 release would be nice. |
|
Or upgrading their existing projects to net standard/core from framework.
Having to use an old prerelease isn't great.
…On Thu, 23 Aug 2018 at 09:06, turbo ***@***.***> wrote:
In fact, there are even people using Nancy for new projects. A formal 2.0
release would be nice.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2872 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APNeJrYGnvytfQe3961b5sAhIdh3mV_Yks5uTcfagaJpZM4SiLQS>
.
|
|
Yeah I second herrgruebner, also using a prerelease version in a mission
critical system given the frequency of commits might not have been the best
course forward for a project and that is fine because things change.
Just flagging this as a production ready release if there is no confidence
in it (otherwise it would have happened already) might give the wron
impression and encourage more people to fully adopt it which might do more
harm than good if the community is no longer there to actively fix issues.
On Thu., 23 Aug. 2018, 7:42 am herrgruebner, <[email protected]>
wrote:
… Or upgrading their existing projects to net standard/core from framework.
Having to use an old prerelease isn't great.
On Thu, 23 Aug 2018 at 09:06, turbo ***@***.***> wrote:
> In fact, there are even people using Nancy for new projects. A formal 2.0
> release would be nice.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#2872 (comment)>,
or mute
> the thread
> <
https://github.com/notifications/unsubscribe-auth/APNeJrYGnvytfQe3961b5sAhIdh3mV_Yks5uTcfagaJpZM4SiLQS
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2872 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AND4tW7Wbuc4vw9MoifrFkboMm0bjn4Tks5uTdA3gaJpZM4SiLQS>
.
|
|
AFAIK there is an active community asking for a new release. If someone is not willing to use Nancy anymore, he/she is more than free to (not?) do so. |
|
Yeah, at this rate I am intending to migrate away from nancy, and I don't
think I'll make anything new with it. The .net framework -> .net standard
migration was enough of a headache without having to swap out Nancy at the
same time, which is why I haven't already.
Although from what's been said earlier in this issue, nancy 2 is ready for
release, and people do want it. If there's no further support, that's fine,
but if the work's been done and people want it, I think it makes sense to
release.
On Thu, 23 Aug 2018 at 09:53, Sebastian Andres <[email protected]>
wrote:
… Yeah I second herrgruebner, also using a prerelease version in a mission
critical system given the frequency of commits might not have been the best
course forward for a project and that is fine because things change.
Just flagging this as a production ready release if there is no confidence
in it (otherwise it would have happened already) might give the wron
impression and encourage more people to fully adopt it which might do more
harm than good if the community is no longer there to actively fix issues.
On Thu., 23 Aug. 2018, 7:42 am herrgruebner, ***@***.***>
wrote:
> Or upgrading their existing projects to net standard/core from framework.
> Having to use an old prerelease isn't great.
>
> On Thu, 23 Aug 2018 at 09:06, turbo ***@***.***> wrote:
>
> > In fact, there are even people using Nancy for new projects. A formal
2.0
> > release would be nice.
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <#2872 (comment)>,
> or mute
> > the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/APNeJrYGnvytfQe3961b5sAhIdh3mV_Yks5uTcfagaJpZM4SiLQS
> >
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#2872 (comment)>,
or mute
> the thread
> <
https://github.com/notifications/unsubscribe-auth/AND4tW7Wbuc4vw9MoifrFkboMm0bjn4Tks5uTdA3gaJpZM4SiLQS
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2872 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APNeJuFm5BpQy1TZaAhfbKtv0PrFfTsMks5uTdLAgaJpZM4SiLQS>
.
|
|
Andreas and I intend to look at this when we are both back off holiday, there's some things that need updating so they work with the latest bits (again), then we will put a release out. |
|
Any update? |
|
Yeah this is the first I've seen about Patreon. Unfortunately I've also started converting my projects because I thought this wasn't actively developed anymore. I have the same Razor issue that I posted about in April of 2017 still open. |
|
Yes, this is sad. I have also started to port my projects. I am currently looking at using Asp.Net Core with Carter. |
|
Nancy just works and if you use docker/mono imo you need not worry too much about the project being maintained as you define the environment and don’t have to worry about OS upgrades. Every bit of software has a limited shelf life anyway. The people working on Nancy did this out of their own time and if they’re busy making money now good luck to them. They don’t need to answer to anyone either. |
Absolutely right. Offering OSS does not obligate you to spend your free time with free-of-charge support as well. But: If the maintainers of an OSS project do not answer questions for an extended period of time that would be a strong indicator that I should look elsewhere for a suitable solution to my problems. With this kind of radio silence I would not start a new project using Nancy@NetCore. |
|
Totally agree, they don'y have to work in Nancy anymore, but at least, they clould crearly state what is happening with this framnework and if there is any plan or not |
|
Before this turns into an argument, does anyone active on this issue actually want to help get this done? It would be good to get a netstandard 2 (or 2.1?) release done, including all the sub projects, but I have (intentionally) done very little with netcore etc. so far, and had nothing but hassle when I have used it, its not something I can just crank out. |
|
I have some experience with netstandard and .net core so I could help somehow, but I am going to require some guidance... |
|
If you look at So the answer is perhaps to have a consolidated effort to raise some funds or pay a monthly subscription towards development *. How many people/companies would pay 50/100 per month for this? *I'm assuming that the devs would want this ...but maybe not. We can ask after we get some commitment. |
|
as an individual i'd be willing to pay some amount per month |
|
I'm already contributing a small monthly amount via Patreon but would be willing to help get this working. We've come to love Nancy and use it alot. Specifically how great it is to test as compared to ASP.NET Core. Being a TDD shop this is super important to me. Is there a place where I can see what works is remaining for this? Or is it more just get in there and make it work? |
|
@khellang @thecodejunkie @jchannon any update regarding a 2.0 production release? |
|
I am also keeping an eye on this thread. We are fully committed using Nancy in our organisation. |
|
@PedreHavenga We ended up switching to Carter, which provides Nancy like syntax on top of ASP.NET Core routing. Check it out: https://github.com/CarterCommunity/Carter |
|
Can a list of issues be associated to this so people know what needs doing / completing for a 2.0 release? It's about time it got finalised. |
|
You mean like this milestone? |
I can maybe get a Dev or two to work on small issues if we can get a list of Tasks/Bugs that needs to be done to get V2 ready for Release. This will be slow going but we can give it a shot. |
|
At least a year without a response from the maintainers makes it clear Nancy is dead. My recommendation is to use https://github.com/CarterCommunity/Carter |
|
I suggested some help from my side several months ago. This help is still on the table in order to release Nancy, in this case working for .net core 3 |
I've been building web apps with Nancy for years, and I'm genuinely sad to see this - it's certainly not on the "super duper happy path" now 😞 In years past, ASP.NET just wasn't extensible enough to support a lot of scenarios elegantly, but Nancy was unopinionated and had an extensibility point for every occasion. Now, ASP.NET Core takes extensibility seriously (the fact Carter even exists is testament to that), and is finally in great shape - this has undoubtedly played a large part in the decline in popularity of Nancy, and indeed of the morale of the devs. So while Nancy has been a prominent and much loved and library for almost a decade, as sad as it is, I can at least understand how it's gotten this way. I would however strongly urge the main devs to make a decision and comment on the current situation, ending a year of uncertainty one way or another. |
|
I still want to put another release out, probably just of the "core" of Nancy (so no additional container support etc.), but every time I've tried to use .net core I've ended up in a world of pain so I generally avoid it. Last time I chatted to @jchannon he mentioned that the main core seemed to build and work ok with the latest bits, if that's still the case I can probably manually package up a release, if that's not the case then I will need someone's help to get a list together of what needs fixing purely to get it to work (probably) netstandard 2.0. |
|
@grumpydev FWIW, I've been using |
|
@cocowalla so if we were to just put out the core nancy packages of -barneyrubble out as 2.0 "final" would that be acceptable, at least as a "first step" ? I still use Nancy every single day, and it still works brilliantly for me, but I don't use .net core for the reasons previously mentioned - I'll return to .net core at some point, but at the moment the amount of friction it gives me just isn't worth my time/frustration, so I need help in .net core/netstandard specific stuff. |
|
So currently our latest is 2.0-clinteastwood and that is stable for my part. There have been a few minor changes I believe since that went out. As long as you have .NET and .NETCore installed on a Windows box you should be able to build it fine. I've just tested on OSX for netcore and all was fine. Can't build .NET as I'm on OSX |
|
@grumpydev @jchannon yes, in the short term what people really want is a production-ready version of 2.0 on NuGet. Beyond that though, it would be great if you (and/or the other core maintainers) got together and publically said something about the future of Nancy. Is there a roadmap? Will it continue to be maintained? Will 2.0 be considered "completed software", with just bugfixes? So many questions from the community 👐 |
|
@grumpydev I have been using the build 2.0.0-pre1911 from your MyGet feed in production for about a year. This build is much newer than even the "clinteastwood" release, and it fixed something important for me; unfortunately, I forget exactly what (maybe a build issue?). I would be happy to see this build promoted to release status. Edit: I should have clarified: I have been running this build on both netcoreapp2.x and net471 without a problem! |
|
Thanks for the comments folks, I will be taking a look Saturday morning (UK time). |
|
Some packages are still verifying, but I've just pushed v2.0.0 to nuget based off the latest master. |
|
This is awesome, thanks a ton @grumpydev ! Just upgraded 2 of my projects from clinteastwood. |
|
Just tested on a brand new netcoreapp 2.2 on osx and al fine!
…On Sat, 27 Apr 2019 at 12:01, Matthieu Barthélemy ***@***.***> wrote:
This is awesome, thanks a ton @grumpydev <https://github.com/grumpydev> !
Just upgraded 2 of my projects from clinteastwood.
Tests pass and everything seems to be working well.
The only change I had to make was to set excludeNullValues in
Nancy.Json.JsonConfiguration.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2872 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAZVJX767O5CWVBKL2VWJLPSQW65ANCNFSM4EUIWQJA>
.
|
|
Even though I have used |
|
@zulq strongly feeling the same. We use Nancy every day of the week here and if anything, we plan to increase our use of Nancy for example by using it as an embedded HTTP server in various products (databases etc...), in addition to the fact that all our web projects (even new and upcoming ones) are and will continue to be based on Nancy. Beyond the beauty of its paradigm, its versatility, its lightweight nature, its comprehensive happy-path, and its flexibility, there is also the fact that the source code of Nancy is what I call "simply open source". Certain codebases are so complex that they are for all practical purposes closed-source since there is no way one will ever have the budget to dig into them let alone adjust them to meet his needs. However, Nancy has a small and easy to understand codebase (in addition to being built for extensibility right from the start) So to me Nancy shouldn't go anywhere. It is done software and does not need to evolve much. I see it as awk and grep, it's not because it is not updated often that it is any less relevant. It is simply that the product has become mature and stable. Just providing my feedback. |
|
I have created A big catch is that Reference: |
and others
2.0.0-clinteastwood was released more than a year ago :(
The text was updated successfully, but these errors were encountered: