Conversation
| * CompletionListener async send support | ||
| * Shared Subscription/Consumer | ||
| * JMSContext support in pool | ||
| * [6.6.0](https://github.com/apache/activemq/milestone/4) |
There was a problem hiding this comment.
I don't think we should mark version this far out, instead share a 'Feature Backlog' or 'Planned Features'.
There was a problem hiding this comment.
That's a fair point. I think we should keep the next two major releases to give perspective and have a list of planned features/ideas.
Thoughts ?
|
I think we should give some thought to website organization around the movement of planned features -> scheduled features (ie assigned a version number -> released features. This would allow users that are casually following ActiveMQ to have an easy way to know when features were added or what the minimum version is required. Perhaps also tagging features with things like 'observability', 'ha', 'performance', 'scalability' would help inform users the benefit of new features. imo we probably need a table like on the JMS2 page |
|
@mattrpav For website organization, I agree but I would do that in a follow up PR (see the discussion on the dev@ mailing list). For now, waiting a larger website effort, I would keep the roadmap on a single page. The table and tagging are good ideas. Let me update that way. Thanks ! |
|
@jbonofre that sounds good-- is there a way to configure the stale bot to ignore proposal issues and WIP PRs? |
|
@mattrpav Great idea ! The issues are not closed by the stale bot (just "flagged"). I think I can also update the stale workflow to ignore some labels. Let me take a look. |
I think going forward PRs are that are still a WIP should be marked as draft status. This probably would make it easier to not close and also lets reviewers know it's not ready to review yet. |
3 participants
The purpose is to give high level visibility to the community, encouraging contributions and giving perspective.