On 09/05/2015 00:55, Joao Eduardo Luis wrote:
A command being DEPRECATED must be:
- clearly marked as DEPRECATED in usage;
- kept around for at least 2 major releases;
- kept compatible for the duration of the deprecation period.
Once two major releases go by, the command will then ente
On 05/09/2015 09:57 AM, Loic Dachary wrote:
> Hi,
>
> On 09/05/2015 01:55, Joao Eduardo Luis wrote:
>> This approach gives a lifespan of roughly 3 releases (at current rate,
>> roughly 1.5 years) before being completely dropped. This should give
>> enough time to people to realize what has happen
Hi,
On 09/05/2015 01:55, Joao Eduardo Luis wrote:
> This approach gives a lifespan of roughly 3 releases (at current rate,
> roughly 1.5 years) before being completely dropped. This should give
> enough time to people to realize what has happened and adjust any
> scripts they may have.
That soun
On 09/05/15 01:28, Gregory Farnum wrote:
On Fri, May 8, 2015 at 4:55 PM, Joao Eduardo Luis wrote:
All,
While working on #11545 (mon: have mon-specific commands under 'ceph mon
...') I crashed into a slightly tough brick wall.
The purpose of #11545 is to move certain commands, such as 'ceph sc
On Fri, May 8, 2015 at 4:55 PM, Joao Eduardo Luis wrote:
> All,
>
> While working on #11545 (mon: have mon-specific commands under 'ceph mon
> ...') I crashed into a slightly tough brick wall.
>
> The purpose of #11545 is to move certain commands, such as 'ceph scrub',
> 'ceph compact' and 'ceph s
All,
While working on #11545 (mon: have mon-specific commands under 'ceph mon
...') I crashed into a slightly tough brick wall.
The purpose of #11545 is to move certain commands, such as 'ceph scrub',
'ceph compact' and 'ceph sync force' to the 'mon' module of the ceph-tool.
These commands have
