The first thing I would offer is that the felix project is an OSGi project and with that it follows OSGi Semantic Versioning ( https://www.osgi.org/wp-content/uploads/SemanticVersioning.pdf)
The effect of semantic versioning to API design is dramatic in that APIs are designed to be concise and cohesive and results in the very rare need to do wide ranging refactorings. If you look across the felix project (or similarly well structured and OSGi projects) you should note a dramatically reduced amount of large scale refactoring. Most refactoring is limited to single or very few bundles at a time. I'm sure there are others who can share more details about your specific questions about JIRA and commit practices, but I don't recall any specific process for those (but I'm pretty new to it so...) - Ray On Mon, May 2, 2016 at 5:25 PM, Miles Teg <[email protected]> wrote: > Hello Everyone, > > I'm part of a team trying to analyse the effects of refactoring on large > codebases. In this regard, we are analysing the Felix project and its > JIRA tickets. > > We would like to know: > i) Do you follow a particular conventions for changes that are > refactorings: e.g. special ticket type or commit messages > ii) Are there specific tickets that are examples of large-scale > refactorings that were done with the intention of improving > maintainability. > > Would appreciate any pointers in this regard :) > > Thank you in advance, > Miles > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
