Excerpts from Robert Collins's message of 2016-03-02 07:14:19 +1300:
> There is a fixture in pbr's test suite to create keys with out entropy use,
> should be easy to adapt for user by Reno's tests.
That's likely where I got the original version of the one in reno now.
Doug
> On 1 Mar 2016 6:52
There is a fixture in pbr's test suite to create keys with out entropy use,
should be easy to adapt for user by Reno's tests.
On 1 Mar 2016 6:52 AM, "Thomas Goirand" wrote:
> On 02/29/2016 10:31 PM, Doug Hellmann wrote:
> >>> Give this a try and see if it works any better:
> >>> https://review.op
On 02/29/2016 10:31 PM, Doug Hellmann wrote:
>>> Give this a try and see if it works any better:
>>> https://review.openstack.org/285812
>>
>> Oh, thanks so much! I'll try and give feedback on review.d.o. Is the
>> issue around the (missed) use of --debug-quick-random?
>>
>> Why do we need Reno uni
Excerpts from Thomas Goirand's message of 2016-02-29 15:15:10 +0800:
> Hi Doug,
>
> Thanks for your reply, it's much appreciated!
>
> On 02/28/2016 11:40 PM, Doug Hellmann wrote:
> > Excerpts from Thomas Goirand's message of 2016-02-28 22:56:51 +0800:
> >>> I believe Thomas is referring to:
> >>>
On 02/28/2016 11:26 PM, Doug Hellmann wrote:
> The plan is to build setuptools integration into reno so that when
> we build our sdists they include a cache file of the data that reno
> derives from the git history, so that without git present reno can
> use the cache file instead of the git histor
Hi Doug,
Thanks for your reply, it's much appreciated!
On 02/28/2016 11:40 PM, Doug Hellmann wrote:
> Excerpts from Thomas Goirand's message of 2016-02-28 22:56:51 +0800:
>>> I believe Thomas is referring to:
>>>
>>> https://bugs.launchpad.net/reno/+bug/1520096
>>
>> The funny part about this
Excerpts from Doug Hellmann's message of 2016-02-28 10:40:44 -0500:
> Excerpts from Thomas Goirand's message of 2016-02-28 22:56:51 +0800:
> > On 02/28/2016 01:18 AM, Davanum Srinivas wrote:
> > > Thomas,
> > >
> > > Please try and let use know what kind of problems you see in Debian as
> > > proj
Excerpts from Thomas Goirand's message of 2016-02-28 22:56:51 +0800:
> On 02/28/2016 01:18 AM, Davanum Srinivas wrote:
> > Thomas,
> >
> > Please try and let use know what kind of problems you see in Debian as
> > projects have already switched to reno.
>
> Dims,
>
> Unfortunately, if I wrote ab
Excerpts from Thomas Goirand's message of 2016-02-28 01:09:36 +0800:
> On 02/26/2016 08:34 PM, Doug Hellmann wrote:
> > We implemented reno for this cycle to replace the old wiki-based
> > system for writing release notes for deployers, operators, and
> > end-users.
>
> Is the fact that Reno does
On 02/28/2016 01:18 AM, Davanum Srinivas wrote:
> Thomas,
>
> Please try and let use know what kind of problems you see in Debian as
> projects have already switched to reno.
Dims,
Unfortunately, if I wrote about this, that's because I tried, and
experienced not very nice things packaging Mitaka
- Original Message -
> From: "Davanum Srinivas"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> Thomas,
>
> Please try and let use know what kind of problems you see in Debian as
> projects have already switched to reno.
>
> Thanks,
> Dims
I believe Thomas
Thomas,
Please try and let use know what kind of problems you see in Debian as
projects have already switched to reno.
Thanks,
Dims
On Sat, Feb 27, 2016 at 9:09 AM, Thomas Goirand wrote:
> On 02/26/2016 08:34 PM, Doug Hellmann wrote:
>> We implemented reno for this cycle to replace the old wiki
On 02/26/2016 08:34 PM, Doug Hellmann wrote:
> We implemented reno for this cycle to replace the old wiki-based
> system for writing release notes for deployers, operators, and
> end-users.
Is the fact that Reno does "git log" when building the docs a solved
problem? Because from my past experienc
Excerpts from Monty Taylor's message of 2016-02-26 11:07:29 -0600:
> On 02/26/2016 10:41 AM, Doug Hellmann wrote:
> > Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400:
> >> On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis
> >> wrote:
> >>
> >>> On Fri, Feb 26, 2016 at 09:03:49AM
On Fri, Feb 26, 2016 at 1:07 PM, Monty Taylor wrote:
> On 02/26/2016 10:41 AM, Doug Hellmann wrote:
>>
>> Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400:
>>>
>>> On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis
>>> wrote:
>>>
On Fri, Feb 26, 2016 at 09:03:49AM -0600, Bran
On 02/26/2016 10:41 AM, Doug Hellmann wrote:
Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400:
On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis
wrote:
On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote:
On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann
wrote:
I'v
Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400:
> On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis
> wrote:
>
> > On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote:
> > > On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann
> > > wrote:
> > >
> > > > I've had a few conv
On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis
wrote:
> On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote:
> > On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann
> > wrote:
> >
> > > I've had a few conversations recently about "appropriate" content for
> > > release notes, so I thought
On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote:
> On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann
> wrote:
>
> > I've had a few conversations recently about "appropriate" content for
> > release notes, so I thought it was worth starting a separate thread here
> > to clarify.
> >
> >
On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann
wrote:
> I've had a few conversations recently about "appropriate" content for
> release notes, so I thought it was worth starting a separate thread here
> to clarify.
>
> We have 3 potential audiences for release notes:
>
> 1. Developers consuming l
I've had a few conversations recently about "appropriate" content for
release notes, so I thought it was worth starting a separate thread here
to clarify.
We have 3 potential audiences for release notes:
1. Developers consuming libraries or other code directly.
2. Deployers and operators.
3. End-
21 matches
Mail list logo
