<br><br><div class="gmail_quote">2009/12/14 micah anderson <span dir="ltr"><<a href="mailto:micah@riseup.net">micah@riseup.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Excerpts from Nigel Kersten's message of Mon Dec 14 12:44:41 -0500 2009:<br>
<div class="im">> Andy and I have set aside Thursday morning PST (GMT - 8) to get the backlog<br>
> out of the way for the puppet packages.<br>
<br>
</div>Great. I will see if I can also be available to work at this time.<br>
<div class="im"><br>
> On the agenda so far:<br>
><br>
> * add the recent patch that was requested for puppetrun with tags<br>
> * Provide more of the ext/ directory in examples or as built in functions<br>
> (based on discussion on puppet-dev list upstream)<br>
> * split out vim/emacs support into separate packages<br>
> * refactor packages so that "tools are distinct from services"<br>
> * create one package for the puppet service, one for the puppetmaster<br>
> service, and one common package both depend on.<br>
<br>
</div>Although I support this idea, i'm wondering how the drive by upstream<br>
towards a merging into one command (puppetmaster) will impact this<br>
work... in particular, I wonder if it might be wasted if upstream is<br>
going to change everything soon.<br></blockquote><div><br></div><div>That was one reason I listed it towards the end of the list :)</div><div><br></div><div>It won't happen in the 0.25.x lifetime though, so we can always revisit this next major version, assuming that upstream gets all this done in time for "rowlf" the next major version.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
On another subject, I had another thought, which was to go through and<br>
cherry-pick fixes from the upcoming 0.25.2 and push them out to Debian<br>
before 0.25.2 is released. It seems like 0.25.2 is still a little ways<br>
off, but there are some particularly annoying issues in 0.25.1 that have<br>
received commits to fix them, and have been tested. I know I've reported<br>
a few and am running a multi-patched version that fixes various<br>
issues. I've done this in the past, and it worked fairly well.<br></blockquote><div><br></div><div>Yep. I'm planning to get a sense of how far 0.25.2 is out of the rest of the upstream community today.</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
micah<br>
</font><br>_______________________________________________<br>
Pkg-puppet-devel mailing list<br>
<a href="mailto:Pkg-puppet-devel@lists.alioth.debian.org">Pkg-puppet-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-puppet-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/pkg-puppet-devel</a><br>
<br></blockquote></div><br>