Hi Dave :)
On 5 May 2015 at 10:37, Dave Walker wrote:
...
> Hey,
>
> As someone that did track master PBR Master for internal cross-project
> builds during the SemanticVersioning ping-pong, I have to agree that
> having a core tool that should be pretty static in feature deliverable
> be a regula
On 4 May 2015 at 23:01, Jeremy Stanley wrote:
> On 2015-05-05 07:53:20 +1200 (+1200), Robert Collins wrote:
> [...]
>> release weekly
> [...]
>
> I'm fine with releasing weekly when there's something to release,
> but as PBR is somewhat stabilized and relatively tightly scoped I
> _hope_ that we g
On 2015-05-05 07:53:20 +1200 (+1200), Robert Collins wrote:
[...]
> release weekly
[...]
I'm fine with releasing weekly when there's something to release,
but as PBR is somewhat stabilized and relatively tightly scoped I
_hope_ that we get to the point where we don't have bugs or new
features in P
On 05/04/2015 04:15 PM, Robert Collins wrote:
> On 5 May 2015 at 08:12, Monty Taylor wrote:
>> On 05/04/2015 03:53 PM, Robert Collins wrote:
>
>> I'm fine with that in principle - I tend to release personal libraries
>> pretty much as soon as something interesting hits them. I have no
>> personal
On 5 May 2015 at 08:12, Monty Taylor wrote:
> On 05/04/2015 03:53 PM, Robert Collins wrote:
> I'm fine with that in principle - I tend to release personal libraries
> pretty much as soon as something interesting hits them. I have no
> personal fear of high release counts.
>
> I'm not sure I 100%
On 05/04/2015 03:53 PM, Robert Collins wrote:
> Hi, I'd like to talk about how often we can and should release pbr,
> and what criteria we should use for 1.0.
>
> tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0
> immediately.
>
> pbr, like all our libraries affects everythi
On 5 May 2015 at 08:04, Clark Boylan wrote:
>
>
> On Mon, May 4, 2015, at 12:53 PM, Robert Collins wrote:
> I don't understand what you mean by "zero real world testing of master".
> We test that pbr can make sdists and install packages on every change to
> master before merging those changes. Th
+1 to call the current master as 1.0
+1 to more frequent releases (not sure if it should be every monday though!)
-- dims
On Mon, May 4, 2015 at 3:53 PM, Robert Collins
wrote:
> Hi, I'd like to talk about how often we can and should release pbr,
> and what criteria we should use for 1.0.
>
> tl;
On Mon, May 4, 2015, at 12:53 PM, Robert Collins wrote:
> Hi, I'd like to talk about how often we can and should release pbr,
> and what criteria we should use for 1.0.
>
> tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0
> immediately.
>
> pbr, like all our libraries affe
Hi, I'd like to talk about how often we can and should release pbr,
and what criteria we should use for 1.0.
tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0
immediately.
pbr, like all our libraries affects everything when its released, but
unlike everything else in oslo, it
10 matches
Mail list logo
