I am *not* suggesting starting over. I am suggesting:<br><br>a. Check in the classic template from the roundup version you started with.<br>b. Branch it to 'ours'.<br>c. Check out all of ours, untar the prototype on top of it, and check it in.
<br>d. Deploy the prototype.<br><br>When a new roundup is released, check the template portion in on top of (a) and push changes to 'ours'. During resolution of these changes you can of course decide you don't want them but at least you know what they are.
<br><br>I don't think it has been a 'long time' since the classic template got changed. I think it happens in almost every release. <br><br><div><span class="gmail_quote">On 11/1/06, <b class="gmail_sendername">Stefan Seefeld
</b> <<a href="mailto:seefeld@sympatico.ca">seefeld@sympatico.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Paul Dubois wrote:
<br><br>> Truth be told I have only once had to modify the runtime. However, like<br>> most<br>> people I started with some instance of the classic template, and modified<br>> it, and there are LOTS of times where new roundup releases have changes to
<br>> the classic template, often required to match the runtime. But unless you<br>> use source code control, you don't know what they are.<br><br>I don't think any changes to the runtime requires changes on the templates.
<br>At least, that hasn't happened for a long time, as roundup grew more and<br>more stable. What happens, of course, is that the vanilla templates themselves<br>get more sophisticated over time.<br>However, as I expect us moving away from these default templates rather quickly,
<br>I'm not sure merging in new features is the most efficient way to enhance our<br>templates.<br><br>> If you started with the demo tracker you started with a slightly modified<br>> version of 'classic'.<br>> I'm suggesting that it is this classic template we need to start with so
<br>> that when new versions of it come out we're ok. I think in principle one<br>> should track the release runtime too but it probably isn't necessary.<br><br>I think we should start with the tracker instance we already have (which Erik
<br>put together for the prototype, and to which I contributed some template<br>enhancements). There is no reason to start over again, in particular, as<br>criticism and enhancement requests were made based on that instance.
<br><br>Regards,<br> Stefan<br><br>--<br><br> ...ich hab' noch einen Koffer in Berlin...<br>_______________________________________________<br>Tracker-discuss mailing list<br><a href="mailto:Tracker-discuss@python.org">
Tracker-discuss@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/tracker-discuss">http://mail.python.org/mailman/listinfo/tracker-discuss</a><br></blockquote></div><br>