cshannon commented on PR #1172: URL: https://github.com/apache/activemq/pull/1172#issuecomment-2317560930
The problem here is the state goals you just listed argue for NOT releasing this. Releases are for delivering to end users, but the goal here is not that. The goals are for profiling, testing, unit tests and for other contributors to get involved. The more I think about this the more I think it's just a really bad idea to deliver something that is completely untested and not even close to ready and likely has actual problems to end users. Instead i think a better approach is what we did on Accumulo when we had our long running "elasticity" branch. We can create a branch for this work in repo that way others can contribute and we can work on the feature until it's closer to being ready. 1. We should create a new branch (call it something like virtual-threads or whatever you want) and use that as the basis of this work. 2. We can keep it up to date by periodically merging main into the branch (merge only, no rebases as we don't want to break history) 3. Developers can open up Pull Requests against this new branch for virtual thread changes so that we can work on pieces at a time and merge them in as they are done. 4. When it's ready, we merge this branch back into main. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
