obsolete markers with mq

[Gregory Szorc]

On 6/23/14, 9:19 AM, Pierre-Yves David wrote:
>
>
> On 06/23/2014 05:54 AM, Gregory Szorc wrote:
>>  From the I-know-this-is-probably-a-bad-idea department, I created a
>> proof-of-concept extension for writing obsolescence markers from mq [1].
>
> Expected result: http://www.bite.ca/wp-content/uploads/2014/04/tVr1diN.gif
>
>
> the major issue with MQ and obsolescence marker and evolution is cycle.
> MQ is perfectly capable (and trying hard) to recreate changeset with the
> same hash than before. And you cannot change that as is would be a
> massive backward compat breakage.
>
> Because of this, this are very like to create messy obsolescence cycle.
> A pretty bad idea.

I hadn't considered this. That's a very good reason why I should delete 
this extension right now.

> It may be time to move people to Evolve ?

I'm not sure if everyone is ready for evolve yet. But I think we can 
easily make that case that bookmark or shelve based development is 
better than mq. That's the direction I'll be nudging Mozillians towards.