We would (my company) would like to see the keyword support expanded,
best would be the full, flexible, user defined keywords but at least the
$Header$ expansion (a different format of the info in $Id$ but the one
we have used in CVS for 8 years or so).
If I have to I can either switch to $Id$ (and fix a bunch of scripts
that are dependent on Header) or patch subversion to support Headers. I
know that others have said that because the keyword system needed a
major rework nothing should be done for 1.0.
On Wed, 2004-03-31 at 21:41, kfogel@collab.net wrote:
> Hmmm. You know what? Let's just have the roadmap discussion here.
>
> I've removed the "[placeholder]" bit from the Subject line, but left
> other threading metadata intact.
>
> Originally, I had wanted to come back to the list with a beautiful,
> shiny, detailed proposal with lots of justifications and subpoints and
> whatnot. But the responses so far show that many people *already*
> have ideas for 1.1. Therefore, it's probably better to figure out the
> roadmap iteratively on this list (Greg Stein suggested the same in a
> private mail). Sure, it may take longer, but everyone will have a
> stake in the final result.
>
> Here's what we've got so far. If I left anything out, it's only by
> accident, please follow up with the missing item. I haven't attached
> the names of the suggesters, since it's the suggestions themselves
> we're interested in:
>
> * l10n (also known as i18n or "that gettext thang")
> * Locking (reserved checkouts)
> * Issue 1093 and friends (diff-follows-copy-history, etc)
> * Straighten out Java bindings
> * Improved release procedures & scripts
> * Full DeltaV compliance (called "pie in the sky" :-) )
> * In-repos ACLs (may be intertwined with reserved checkouts work)
> * True rename support, at least in the repository
> * symlink support
> * "What about plug-in client-side diffs?"
> * Fix N specific bugs (many in issue tracker are already marked as
> "1.1", though that set is not written in stone of course)
>
> Let's not get down to actual voting or anything like that at this
> point. And, let's not talk about dates just yet. Rather, let's start
> with some questions:
>
> Does anyone see anything on this list that looks hard or impossible,
> given our API guidelines, for a 1.1 release?
>
> Do we think anything on this list would definitely take more than
> (say) six months to design and implement?
>
> Are there other things you would like to see on this list?
>
> (Even among items that everyone agrees are possible for 1.1, there
> will probably have to be a winnowing process eventually. But let's
> start by getting all the ideas on the table, then see what looks
> realistic.)
>
> All right, let's hear it!... :-)
>
> -Karl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
--
It is MDT, Inc's policy to delete mail containing unsolicited file
attachments.
Please be sure to contact the MDT staff member BEFORE sending an e-mail
with
any file attachments; they will be able to arrange for the files to be
received.
This email, and any files transmitted with it, is confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you have received this email in error, please advise
postmaster@mdtsoft.com
<mailto:postmaster@mdtsoft.com>.
Philip W. Dalrymple III <pwd@mdtsoft.com>
MDT Software - The Change Management Company
+1 678 297 1001
Fax +1 678 297 1003
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 1 20:14:14 2004