On Mon, Oct 22, 2012 at 1:57 PM, Jeff Weiss <[email protected]> wrote:
> Getting #17129 into this iteration would be awesome.
>
> #17129 - SSL REST API bails out completely on permissions errors
>
> http://projects.puppetlabs.com/issues/17129

We might have space for this.

>
> We've noticed that if there is any problem reading any of the CSRs (maybe a
> permissions problem or misnamed), the entire call blows up and none of the
> readable CSRs are returned in the collection. We (the PE team) were going to
> develop a patch, and submit it. If y'all can get to it before us, then
> that's even awesomer-er.  If not, please let us know the pull request
> submittal deadline for 2.7.20.
>

I'm looking at being able to cut the RC next week. So let's say the
submission deadline is EOD Wednesday next week.

> Thanks,
>
> Jeff Weiss
> Puppet Labs, Inc.
> [email protected]
>
> On Mon, Oct 22, 2012 at 12:59 PM, Andy Parker <[email protected]> wrote:
>>
>> In an effort to become more transparent I'm going to start trying to
>> write up a periodic update on what the Puppet Labs developers are
>> going to be concentrating our time on. I'm hoping that this will give
>> everyone a bit of insight into things, an opportunity to help us out
>> on what we are doing (code, comments, whatever), and allow others to
>> choose things to work on that fit into a larger direction that we are
>> working on. I'm just taking a first stab at this here, let me know if
>> this is useful or if any other information about what we are planning
>> might be good to include.
>>
>>
>> Work for this iteration:
>>
>> Our iterations are fortnightly at the moment. For this fortnight we
>> have chosen to concentrate on getting 2.7.20 ready for release. 2.7.20
>> will be the last "planned" release of the 2.7 series, after this we'll
>> be concentrating on moving forward in the 3 series and only obvious
>> bugs will be fixed in 2.7.
>>
>> #16581 - SID resolution very slow
>>   * Josh and I are working through this. Josh has already put together
>> a patch that appears to fix the problem, which looks to be an issue
>> with using the WMI interfaces for SID resolution and so are changing
>> to using the native interfaces (I'm not really versed in windows, so
>> Josh can correct me if I am stating this wrong)
>>   * As part of this work we tackled making our Jenkins jobs for
>> windows use Bundler for managing dependencies. I wanted to do that so
>> that the Gemfile wouldn't just rot. Now that it is being used at least
>> a little bit all of the time it should be clear when it stops working.
>>
>> #16791 - Undo breaking changes from the backport of performance fixes from
>> 3.0.0
>>   * As I had promised we did the backport of some of our 3.0.0
>> performance fixes into the 2.7 line. Unfortunately we noticed that we
>> also backported some of the backwards incompatible changes. Oops.
>> Luckily they were noticed and we can fix them up before the release.
>>
>> #16330 - Update ZAML license
>>   * It was pointed out that ZAML, as we had it, was actually licensed
>> as GPL. That was a mistake for us to have GPLd code, and we worked
>> with the ZAML authors who graciously dual licensed it under
>> Apache/GPL. We need to update our ZAML to be in compliance. This was
>> already done as part of the 3.0.0 release and so this is really just a
>> backport of that work.
>>
>> #14822 - Ensure providers can run if features are delivered during a run
>>   * Pull request from Dominic Cleal. I think that all that is needed
>> here is a final run through of the change and a merge.
>>
>> In addition, Jeff McCune is continuing with dealing directly with pull
>> requests submitted and helping get those ready.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Developers" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-dev?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en.

Reply via email to