https://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732014-05-20T19:35:46ZOpen Source Collaboration PlatformAutomated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=55952014-05-20T19:35:46ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>0.3</i> to <i>0.4</i></li></ul> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=61182014-10-31T16:14:18ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Description</strong> updated (<a href="/journals/diff/6118?detail_id=7142" title="View differences">diff</a>)</li></ul> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=66122015-03-02T13:07:51ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>0.4</i> to <i>0.5</i></li></ul> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=66292015-03-05T08:59:03ZS. Meyer zu Borgsensemeyerz@techfak.uni-bielefeld.de
<ul></ul><p>Could it be a first simple solution to simply join multiple "verions"-lists?</p> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=66302015-03-05T09:36:55ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul></ul><p>S. Meyer zu Borgsen wrote:</p>
<blockquote>
<p>Could it be a first simple solution to simply join multiple "verions"-lists?</p>
</blockquote>
<p>This really depends on the mid- and maybe long-term strategy for this project. There are three major possibilities:</p>
<ol>
<li>Implement the feature in the current architecture and code base (as you suggest). I did this in a feature branch but it stretches the current architecture far beyond its original scope.</li>
<li>Implement the feature in the new architecture loosely based on the current code base. I did this in a feature branch as well and it worked quite well. The new architecture solves several other problems as well. For example, distribution version are defined in a single recipe and share most of the definitions like project versions currently already do. As another example, <code>branches</code> and <code>tags</code> are no longer mandatory in projects; instead, distributions can request arbitrary branches, tags or commit without changes to project recipes.</li>
<li>Rewrite the project according to the "new architecture" mentioned in 2) or some other architecture. This would of course allow going about the inclusion feature in the same way as in 2) or in some other smart way.</li>
</ol>
<p>The complications, potential problems and short-term character involved in 1. probably make it not worth the effort.</p>
<p>We attempted to decide between 2. and 3. several times but each time failed to organize the respective meeting. No matter how we decide between 2. and 3., significant effort will be required and the respectively resulting new generator will not be a drop-in replacement, thus another migration will be necessary in addition.</p>
<p>As a result, I think this feature will take some time.</p> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=66332015-03-05T13:04:03ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<ul></ul><p>J. Moringen wrote:</p>
<blockquote>
<p>We attempted to decide between 2. and 3. several times but each time failed to organize the respective meeting.</p>
</blockquote>
<p>Which was also due to holiday of key personnel involved... ;-)</p>
<blockquote>
<p>No matter how we decide between 2. and 3., significant effort will be required and the respectively resulting new generator will <br />not be a drop-in replacement, thus another migration will be necessary in addition.</p>
</blockquote>
<p>This is true. However, this feature may be ranked relatively high on the roadmap for the new build gen architecture / implementation strategy as the lack of it currently impedes scalability of the development process.</p> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=87372016-09-30T08:43:59ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>0.5</i> to <i>0.8</i></li></ul> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=87952016-10-25T10:32:16ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>0.8</i> to <i>0.9</i></li></ul> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=90492017-02-23T10:35:03ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>0.9</i> to <i>1.0</i></li></ul> Automated Build Generator - Feature #1684: Implement "includes" relation for distributionshttps://code.cor-lab.de/issues/1684?journal_id=95952019-01-10T17:27:45ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a href="https://code.cor-lab.de/projects/build-generator/repository/revisions/e536cafea8d4f5a47daf12ccfb905ec363c75a79" class="changeset" title="Added enhancement entry in changes.sexp fixes #1684 * changes.sexp (release 0.26): added enhanc...">e536cafea8d4f5a47daf12ccfb905ec363c75a79</a>.</p>