On 09/07/2009 02:54 AM, Gervase Markham wrote:
> Here's a test for function I've needed from the 3 major Mozilla SCMs
> recently: can it give me an XML or RSS feed of all changes in the entire
> repository (or, perhaps, a separate feed for each branch) from a
> particular date, say, six months ago?
Yeah, I'm pretty sure you can get Atom limited by date. It's not
something that's directly in the UI, but you can just add a few URL
parameters that are probably documented somewhere that I could look up
for you some time, if you'd like. (Or you could ask in #bzr on FreeNode
if the loggerhead devs are around when you ask--beuno is the main one, I
>>> On 9/4/2009 at 04:28 PM, in message <[hidden email]>, Max
Kanat-Alexander <[hidden email]> wrote:
> Okay, we've had this discussion before, but this time, we have to
> actually do it. We've been on CVS for too long--we may be the only
> remaining major Mozilla project still using CVS for primary development.
> We're certainly the only major open source project that I know of and
> interact with regularly that still uses CVS.
I guess I will weigh in.
I personally have no experience with either Hg or bzr and much prefer svn to anything else I have used. My biggest concerns are having IDE support, especially Eclipse since that is my preferred development environment. A quick google search shows that there are clients for both.
Either way, I am going to have to learn a new VCS, but I trust Max's judgement and I like the fact that a company like Canonical is behind it. I know something of the complexity of managing a distribution and if they can apply that understanding to source control, it must have been pretty well thought out.
As for Testopia, I will switch to use whatever Bugzilla goes with as I am rather tied to that platform as it is anyway.
>>> On 9/5/2009 at 11:01 PM, in message <[hidden email]>, Bill Barry
<[hidden email]> wrote:
> Max Kanat-Alexander wrote:
> > On 09/05/2009 03:43 PM, Bill Barry wrote:
> >> see a testopia repository
> >> that keeps up to date with the changes as they happen).
> > That would depend more upon somebody committing development
> > resources to Testopia than a VCS switch, although switching to a DVCS
> > would certainly have some advantages. I agree it would be nice,
> > though. :-)
> It will be much easier to maintain a fork than it currently is to
> maintain a single giant patch. I pity what Greg has to go through each
> time he attempts to upgrade Testopia. That is a lot of work (which
> wouldn't be nearly so difficult if it was easier to keep up with the
> changes). His latest news was a bit unsettling as far as the future for
> Testopia goes.
Thanks for the thought. :)
I will admit, keeping abreast of what is going on in Bugzilla via CVS even with tools like Bonsai could keep me occupied full time. What I usually end up doing is using a 3 way diff tool like kdiff3 to view the changes to the entire Bugzilla release at once. I then keep a subversion branch that I use to create the patches that I apply to the CVS repository before checking in each change. It certainly isn't ideal and I hope that whatever we come up with is a better solution.