[Infrastructures] isconf deprecates infrastructures.org?

[Daniel Hagerty]

 > This has long been a complaint of mine with the tools I've looked at.
 > I'd really like to be able to inform the tool, make local changes, then
 > check my changes back into the central repository, easily and without a
 > lot of fuss.  Because, invariably, it takes more than one try to get a

    Well, depending on what you mean here, this is kind of what isconf
4 (or whatever it is) is trying to give you, provided that you work
within its constraints.  But by the same token, undoing "oops" as part
of your edit/compile/debug cycle isn't really in scope.  You'd need a
completely different model.  It all depends on what you really mean
when you say the tools aren't that good -- it's true, they aren't, but
what would you like to see them do better, spelled out more precisely?
(and this is the wrong list for such a discussion)

 > particular configuration right and the iteration of "change in repo,
 > manually run tool to update host, reload server, see if it worked" is
 > frustratingly long--even if it's only 30 seconds or so.

    If your edit/compile/debug cycle is 30 seconds, you're doing
peachy.  99.7% of the world has to deal with much longer.