* Dermot McCluskey <[EMAIL PROTECTED]> [2006-04-18 04:06]: > Danek Duvall wrote On 04/13/06 19:51,: > > >But if v1 for ON is just the external read-only mirror repo, then it > >doesn't matter for me -- I just need these things by the time we go > >read-write, and I doubt that'll be an issue. > > Right. But for JDS, we're planning to go live with a read-write > repository for the desktop community members from v1. Which > is why I'm getting a bit fustrated that our requirements are > being brushed aside. If you don't believe that an appropriate balance of features implemented and deferred is being taken, that's a legitimate complaint. The reason I wrote
http://www.opensolaris.org/jive/thread.jspa?threadID=7710&tstart=0 (that is, the first message in this thread) was so that your team could explore its greater needs in a way that could be reused. However, and this aspect should be apparent by now, those needs for precommit hooks are substantially different than the bulk of the consolidations--and therefore do not necessarily claim the global priority that one might locally assign. > Also, which document laid out which features would be in V1 > of the SCM, versus future versions? The minimal feature set was published across two documents in this forum; these were reposted at http://www.opensolaris.org/os/community/tools/scm/ For the most part, with the paths changed as one thread suggested (although I'm not sure we've got the "first repository has no suffix" functionality), these are being used as specs for the implementation. - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ tools-discuss mailing list [email protected]
