| Petya,
To answer your questions. Yes, we would need a bug for the feature patch request. I don’t think it needs to be marked as a hot-bug. I would would need PMC review.
Carl, and others,
Have we done a feature patch since moving to the new CBI infra? I was just wondering if there was a standard procedure that we were following for this, or whether the old standard procedure needs to change.
Neil
Hi all, The JPA Diagram editor is not working for Eclipse Mars 2. As described in Bug 472835, the reason is a buildtime dependency. Few weeks before Mars 2 became GA, I updated the feature level dependency, requiring a newer version of the Graphiti project. I thought that with this change, the whole JPA Diagram editor project will be rebuild, but actually only the diagram editor’s feature was updated. It took me some time to figure out that only features/plugins that contains changes will be automatically rebuild and by that time it was already too late to respin the WTP build. So as Harald Albert has already commented in the bug, the current state of the JPA diagram editor become even worse. That’s why I would like to make a feature patch. The change that will be added with this feature path is a minor and the risk of breaking something is very low. I’ve already submitted it in the master branch and it works fine: I found this wiki, describing how to make a feature patch publicity available, but still have some questions: · Should I open a bug for that issue · Should it be marked as hot-bug · Do I need PMC reviews So, I will be thankful for any other information on how to make a public feature patch. Regards, Petya
|
