You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great to see all the momentum with the new version.
I don’t think this should be a direct port to .net 6. We should take our time to consider if there improvements or changes etc we’d like to make and what new things .net 6 can give us.
Should we have a discussion about how we will approach the code rewrite to .net 6. Are we planning on porting everything from the current 2.x.x release to 3.0.0?
I've been thinking about this, and IMO for the 3.0.0 release we should strive to have no effective breaking changes behaviorally.
If we need/want to tweak the API that would be fine, but the user should not have to think about the changes much.
Afterwards we can start setting up an obsoletion policy and make deeper changes
Sounds good, I think we port everything across to the new solution with the upgraded .net and get everything setup, finish off all the fluff around docs, actions etc. Then take it from there perhaps?
We already have kinda a policy in place if you check #143
Apolgies @marblekirby lots on at work!
I think it has already started with the new solution been created but as far as that im not sure anything else apart from the supporting community stuff has been done.
I'll make a start moving it over to the new solution when i have a spare minute
👋 I followed the breadcrumbs from other issues to get here. Am I correct that the re-write ran out of steam and the project is unmaintained, at this point?
👋 I followed the breadcrumbs from other issues to get here. Am I correct that the re-write ran out of steam and the project is unmaintained, at this point?
Potentially a few people knocking about!?
I've been doing a little work in the background on publishing new versions to NuGet via Github actions & looking into potentially going down the fluent api route
@JoshHiles Great! I just got permission from my company to contribute, so I'll probably pull this into a spike I'm working on next week. Is there a discord or something like that for informal collab?
@JoshHiles Great! I just got permission from my company to contribute, so I'll probably pull this into a spike I'm working on next week. Is there a discord or something like that for informal collab?
If you want to use the discussions area that could work?
Activity
paulbreen commentedon Jul 21, 2021
Great to see all the momentum with the new version.
I don’t think this should be a direct port to .net 6. We should take our time to consider if there improvements or changes etc we’d like to make and what new things .net 6 can give us.
marblekirby commentedon Jul 23, 2021
Should we have a discussion about how we will approach the code rewrite to .net 6. Are we planning on porting everything from the current 2.x.x release to 3.0.0?
M-Zuber commentedon Jul 29, 2021
I've been thinking about this, and IMO for the 3.0.0 release we should strive to have no effective breaking changes behaviorally.
If we need/want to tweak the API that would be fine, but the user should not have to think about the changes much.
Afterwards we can start setting up an obsoletion policy and make deeper changes
JoshHiles commentedon Jul 29, 2021
Sounds good, I think we port everything across to the new solution with the upgraded .net and get everything setup, finish off all the fluff around docs, actions etc. Then take it from there perhaps?
We already have kinda a policy in place if you check #143
M-Zuber commentedon Jul 29, 2021
Yeah, sounds like what I had in mind 👍
marblekirby commentedon Sep 19, 2021
@JoshHiles I see alot of tickets open for the fluff around the docs/actions etc but what about the port to latest .net version?.
I am working through the wiki. I see alot of new actions created. What about getting started on the version migration?
JoshHiles commentedon Sep 20, 2021
Apolgies @marblekirby lots on at work!
I think it has already started with the new solution been created but as far as that im not sure anything else apart from the supporting community stuff has been done.
I'll make a start moving it over to the new solution when i have a spare minute
mwilson-atlassian commentedon Dec 5, 2023
👋 I followed the breadcrumbs from other issues to get here. Am I correct that the re-write ran out of steam and the project is unmaintained, at this point?
JoshHiles commentedon Dec 5, 2023
Potentially a few people knocking about!?
I've been doing a little work in the background on publishing new versions to NuGet via Github actions & looking into potentially going down the fluent api route
mwilson-atlassian commentedon Dec 6, 2023
@JoshHiles Great! I just got permission from my company to contribute, so I'll probably pull this into a spike I'm working on next week. Is there a discord or something like that for informal collab?
JoshHiles commentedon Dec 6, 2023
If you want to use the discussions area that could work?