<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000"> </font>Nonsense. In the past 6 months, just to take three that come to mind, we have closures, native fonts and unloadable smaller traits. There are lots of other things also; go look at the recent changes list. Trunk is actually progressing very nicely.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">You might try contributing code rather than whining at length. It's more fun for everyone. Better for the community</blockquote></div></blockquote></div></div></blockquote><div><br></div>I don't think I can contribute code.</div><div><br></div><div>For example, my contributions to Monticello. In case you don't realise it. Monticello cannot load Monticello, so contributing it to trunk will not work, that is why we developed LPF loading process in the first place. But of course, trunk didn't build on 3.10-build did it, so the process chosen for trunk prevents me contributing towards MC or PackageInfo, two areas that have massive changes (now in the bin)</div><div><br></div><div>My contributions for a Package manager are loadable, [ Installer install: 'Packages'. ] So they don't have any place in the trunk scheme either.</div><div><br></div><div>The trunk process is allowing people that would normally contribute via a changeset to contribute, (well just give me the changesets, then I can use them) and it is enabling people who would normally write a loadable package to contribute, (so just publish the loadable package).</div><div><br></div><div>However, fundamental changes to Monticello, and PackageInfo, you can forget it. Goodness knows how you change compiler stuff.</div><div><br></div><div>Watch this space, I will submit code for Cuis, because that does have a process I can contribute to, i.e. Juan has not defined process for contributions that prevents contributions.</div><div><br></div><div>I always regarded your points as respectable and sensible, so I hope you understand my opinion that the trunk process closed me out. The very ethos of the previous model was to harness all possible contributions, not to prevent people from making them. However I am sure I can rely on you to correct me if I am wrong.</div><div><br></div><div>regards</div><div><br></div><div>Keith<br><div><br></div><div> </div></div></body></html>