#120: Switch to "mtn automate"
----------------------+-----------------------------------------------------
Reporter: dhbaird | Owner: lele
Type: defect | Status: new
Priority: major | Milestone: VersionOne
Component: mtn | Version: 0.9
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Comment (by dhbaird):
Well, on second thought, I can think of a good reason for having two
versions of monotone simultaneously: It means that I can install Tailor
once on my system and simultaneously work on both modules: bug fixes to
monotone.py while also bringing monotoneautomate.py up-to-par with
monotone.py. Then, as soon as "mtn automate" is finished, we can replace
monotone.py with monotoneautomate.py. OTOH, if we just have an entirely
new branch altogether, then the old screen-scraping monotone.py might be
neglected while we focus on the new "mtn automate" branch of monotone.py.
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/120#comment:4>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
