[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

[Matthew Knepley]

On Mon, Mar 11, 2013 at 3:35 PM, Karl Rupp <rupp at mcs.anl.gov> wrote:

> Hi Sean,
>
> >>> Satish, please remove me from petsc-maint. Also, remove me from the
>
>> developers webpage. I have already purged petsc-dev from my system and
>>>> won't be pushing anything else from now on.
>>>>
>>>
>>> Huh, why this? This is not forced change of religion...
>>>
>>
>> Why should I bother? Everyone will listen to Jed anyway. Sorry about the
>> CUDA+cmake patches, by the way, those are gone now.
>>
>
> it will still be possible to work with Mercurial. The need for a
> new/better development model was also based on stability issues repeatedly
> raised by users at SIAM CSE, as you certainly remember.
>

My characterization of it is more that we adopted a particular piece of
technology because we thought
it was better architected and might in the future promise efficiency gains.
I don't think this will be any
more stable than everyone working in different clones for different
projects. The technology here is
lightweight branches, which is supposed to deliver efficiencies not
available to the multiple clone model.
We will see :)

   Matt


> The decision followed a technical evaluation of the workflow, not on a
> 'Sean vs. Jed'-type of personal preference. Thus, you really should not
> take this personal.
>
> Best regards,
> Karli
>
>


-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/98941c84/attachment.html>