Would it be possible/desirable to have a system such that:
* bug fixes for external packages can be still be directly applied and
tested in the Pharo-integrated branch
* the CI workflow generates an updated ConfigurationOf{external package}
that it pushes back to the external package repository?Its a great idea to separate out Configurations to devolve responsibility for sub-packages, but it adds some friction to bug fixing. It "seems" we will have a single branch combining both feature development and bug-fixing, but it would be nicer to have two branches. --------------- On another track, I wonder if it would be useful if a package which is part of a Configuration is made dirty, the Configuration itself could also be marked dirty? cheers -ben On Fri, Feb 6, 2015 at 4:36 AM, Nicolai Hess <[email protected]> wrote: > 14850 <https://pharo.fogbugz.com/default.asp?14850> Integrate GTools > #development > "From this version onwards the development version should be integrated." > > Is this a good idea? Does the #development version always include *all* > the latest > changes, because after Andrei opened > 14866 <https://pharo.fogbugz.com/default.asp?14866> Integrate GTools > (which got integrated in 40475) > I uploaded some changes for issue > 14608 <https://pharo.fogbugz.com/default.asp?14608> > ClassTest>>#testClassRespectsPolymorphismWithTrait failing due to Spotter > methods > I set the status to "Fix Review needed", > > but my changes are integrated in 40475 too! > > I am not satisfied with the way external packages are handled. > 1. if there is not one slice/changeset per issue, it is even less likely > someone will > review the changes. > 2. you don't know who works when on a issue. They are solved in a bulk. > 3. a new configuration might not only includes bugfixes but new features > as well. > 4. often we have unbound globals / undeclared references or other test > failures. > > Can we use the build server for those external projects (like > GToolkitCore, Athens, TxText), > and that if a project makes a new configuration, it uses the same > issue validator for loading and testing that configuration? > > > nicolai > > >
