question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Any plans to release a Milestone version from 2.0 branch ?

See original GitHub issue

On the 2.0 branch we have performed a lot of changes to the Model Interfaces in order to:

  • Have interface that do not extend java.util.Map
  • Have clear behaviour (for example: enforce to create copy of list/maps, return an immutable copy…)
  • Have defined paths for the mutations operation (the consumer of the library have a clear way to add/remove elements in list/maps)

One use case I am looking at is a way to bridge existing OpenAPI libraries into the Microprofile model interfaces. Code should can be written against the Microprofile model interfaces, but the underlying library is Swagger-Core or KaiZen models.

The ultimate goal is to be able to exchange the parsers (Swagger-Parser or KaiZen Parser).

I think I will soon have reached the point where I need a released version taken from the 2.0 branch. Could we create a pre-release (for example version 2.0.M1) and publish it on Maven central?

Because of release schedule of other projects I am working on, I would need it mid-december 2018. Maybe one strategy could be to do it right after the 1.1 release.

I am ready to invest some effort in this. From a GitHub / maven / maven-central point of view doing the pre-release is simple. But because the project is part of a bigger one Microprofile and Eclipse Fundation, I can imagine that my request is a little bit more complex or not possible.

If my proposal is rejected or considered as too complicated, I will consider forking the project and releasing it under an other groupId. Of course when 2.0 is officially released, the fork and the Milestones pre-releases created from this fork will become obsolete.

Thank you for your feedback.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
jminicommented, Dec 16, 2018
1reaction
kenfinnigancommented, Dec 7, 2018

Other specifications have released “Release Candidates” prior to a final release for inclusion in MP.

MP REST did one the other week.

I’m not sure what “process” might be required, but could ask on MP Google Group

Read more comments on GitHub >

github_iconTop Results From Across the Web

2.0 Release Milestone · GitHub
Branch Created: ... AutoRest is making a a few structural changes, along with eliminating some deprecated legacy behavior. Notable changes in this branch:...
Read more >
Projects/SeriesMilestonesReleases - Launchpad Help
Obsolete branches: for major release versions that are now out of date and no longer updated. It's likely that work no longer happens...
Read more >
Milestones - GitLab Docs
A milestone can belong to project or group. You can assign project milestones to issues or merge requests in that project only. You...
Read more >
What is the Correct Way to Version With Issues Under a ...
We are using gitlab and have a "milestone" for version 2.0. ... bump my minor version up when the branch for an issue...
Read more >
Release Processes - OpenStack Releases
Milestone -1¶ · List them using: · Edit the generated file ( /tmp/deliverables. · Between Tuesday and Thursday, merge as soon as possible...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found