Sean Dague wrote:
> On 09/08/2015 03:32 PM, Doug Hellmann wrote:
>> Excerpts from Sean Dague's message of 2015-09-08 14:11:48 -0400:
>>> On 09/08/2015 01:07 PM, Doug Hellmann wrote:
Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500:
> On Tue, Sep 8, 2015 at 9:10 AM, Doug
On 10 September 2015 at 06:18, Doug Hellmann wrote:
> Excerpts from Ben Swartzlander's message of 2015-09-08 22:22:38 -0400:
>> It would be a recognition that most customers don't want to upgrade
>> every 6 months -- they want to skip over 3 releases and upgrade every 2
>>
Excerpts from Ben Swartzlander's message of 2015-09-08 22:22:38 -0400:
> On 09/08/2015 01:58 PM, Doug Hellmann wrote:
> > Excerpts from Ben Swartzlander's message of 2015-09-08 13:32:58 -0400:
> >> On 09/03/2015 08:22 AM, Thierry Carrez wrote:
> >>> Hi everyone,
> >>>
> >>> A feature deprecation
On 09/03/2015 08:22 AM, Thierry Carrez wrote:
> Hi everyone,
>
> A feature deprecation policy is a standard way to communicate and
> perform the removal of user-visible behaviors and capabilities. It helps
> setting user expectations on how much and how long they can rely on a
> feature being
Excerpts from Sean Dague's message of 2015-09-08 14:11:48 -0400:
> On 09/08/2015 01:07 PM, Doug Hellmann wrote:
> > Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500:
> >> On Tue, Sep 8, 2015 at 9:10 AM, Doug Hellmann
> >>>
> >>> I'd like to come up with some way to express the time
On 09/08/2015 03:32 PM, Doug Hellmann wrote:
> Excerpts from Sean Dague's message of 2015-09-08 14:11:48 -0400:
>> On 09/08/2015 01:07 PM, Doug Hellmann wrote:
>>> Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500:
On Tue, Sep 8, 2015 at 9:10 AM, Doug Hellmann
>
> I'd
On 08/09/2015 5:29 PM, Sean Dague wrote:
On 09/08/2015 03:32 PM, Doug Hellmann wrote:
Excerpts from Sean Dague's message of 2015-09-08 14:11:48 -0400:
On 09/08/2015 01:07 PM, Doug Hellmann wrote:
Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500:
On Tue, Sep 8, 2015 at 9:10
Excerpts from Sean Dague's message of 2015-09-08 08:13:14 -0400:
> On 09/03/2015 08:22 AM, Thierry Carrez wrote:
> > Hi everyone,
> >
> > A feature deprecation policy is a standard way to communicate and
> > perform the removal of user-visible behaviors and capabilities. It helps
> > setting user
On 09/08/2015 01:58 PM, Doug Hellmann wrote:
Excerpts from Ben Swartzlander's message of 2015-09-08 13:32:58 -0400:
On 09/03/2015 08:22 AM, Thierry Carrez wrote:
Hi everyone,
A feature deprecation policy is a standard way to communicate and
perform the removal of user-visible behaviors and
On Tue, Sep 8, 2015 at 9:10 AM, Doug Hellmann
>
> I'd like to come up with some way to express the time other than
> N+M because in the middle of a cycle it can be confusing to know
> what that means (if I want to deprecate something in August am I
> far enough through the current cycle that it
On 09/03/2015 08:22 AM, Thierry Carrez wrote:
Hi everyone,
A feature deprecation policy is a standard way to communicate and
perform the removal of user-visible behaviors and capabilities. It helps
setting user expectations on how much and how long they can rely on a
feature being present. It
Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500:
> On Tue, Sep 8, 2015 at 9:10 AM, Doug Hellmann
> >
> > I'd like to come up with some way to express the time other than
> > N+M because in the middle of a cycle it can be confusing to know
> > what that means (if I want to
Excerpts from Ben Swartzlander's message of 2015-09-08 13:32:58 -0400:
> On 09/03/2015 08:22 AM, Thierry Carrez wrote:
> > Hi everyone,
> >
> > A feature deprecation policy is a standard way to communicate and
> > perform the removal of user-visible behaviors and capabilities. It helps
> > setting
On 09/08/2015 01:07 PM, Doug Hellmann wrote:
> Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500:
>> On Tue, Sep 8, 2015 at 9:10 AM, Doug Hellmann
>>>
>>> I'd like to come up with some way to express the time other than
>>> N+M because in the middle of a cycle it can be confusing to
On 2015-09-08 13:32:58 -0400 (-0400), Ben Swartzlander wrote:
[...]
> It makes sense for the community to define LTS releases and coordinate
> making sure all the relevant projects are mutually compatible at that
> release point.
[...]
This seems premature. The most recent stable branch to reach
On 09/08/2015 02:24 PM, Jeremy Stanley wrote:
> On 2015-09-08 13:32:58 -0400 (-0400), Ben Swartzlander wrote:
> [...]
>> It makes sense for the community to define LTS releases and coordinate
>> making sure all the relevant projects are mutually compatible at that
>> release point.
> [...]
>
>
On 3 September 2015 at 08:22, Thierry Carrez wrote:
> ...
> In particular, the current proposal says:
>
> "At the very minimum the feature [...] should be marked deprecated (and
> still be supported) in the next two coordinated end-of-cyle releases.
> For example, a
Hi everyone,
A feature deprecation policy is a standard way to communicate and
perform the removal of user-visible behaviors and capabilities. It helps
setting user expectations on how much and how long they can rely on a
feature being present. It gives them reassurance over the timeframe they
18 matches
Mail list logo