-
Notifications
You must be signed in to change notification settings - Fork 382
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
No new release since April 2018 ... is the project abandoned? #413
Comments
Hi, |
Yeah, sure about that but I was reasoning about a new 1.3.4 or 1.4.0 version without the OpenAPI 3.0 support. |
Yes, but it was the decision by the maintainer and contributor . |
If I was maintainer (and contributor), I would create a 1.3.x branch (or 1.4.x) from the commit just before the first OpenAPI 3.0 contribution and cherry-pick all the subsequent bug fixes not related to OpenAPI 3.0 on it. |
@RobWin do you think that my idea is feasible to apply compatibly with your time? |
Sure, but I just don't have time to do it. |
It's a pity because this cool project has reached a kind of dead state :-( ... and using the master for OpenAPI 3.0 was a mistake because the people who had the commitment for it, now are not working on it for a long time and maybe they won't work anymore. |
Yes I agreee, but if the community is still interested in Swagger2Markup, they can join our Slack Channel, I give them permissions and they can just create this bugfix branch by themselves. |
@RobWin could you please explain what open issues / features needs to addressed in order to finalise OpenAPI v3 support and enable the release to go ahead? Thanks, Andy. |
@andye2004 Have a look at all the stories which are tagged with "Help wanted" |
Hi all,
what's the plan for this project?
I fixed a bug (#410) long time ago (in June) but no new release since April 2018. I see the work around OpenAPI 3.0 support which is even labeled as "help-wanted" so I don't know if it's going to happen soon. What about a new release before it? Or we should just consider this project as abandoned and taking a look at alternatives? @RobWin any thoughts?
The text was updated successfully, but these errors were encountered: