I would be able to help.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bret Pettichord
Sent: Friday, March 10, 2006 3:46
PM
To: [email protected]
Subject: [Wtr-general] Moving to
OpenQA.org
We are in the process of moving many of the services that have been
provided on RubyForge.org over to OpenQA.org. You'll be seeing more and more
signs of this, so i thought i would send out a quick status report. If you have
questions or want to help, please speak up.
Repository
The source repository has been moved to Subversion (SVN) on OpenQA. You can see
it here:
http://www.openqa.org/watir/cvs.action
All of the existing committers who have requested commit access to the new repo
have been given it.
Previously CVS automatically sent email to an email list whenever a change was
made. We don't have that option with SVN right now, but instead there is an RSS
feed which does about the same thing:
http://svn.openqa.org/fisheye/rsscfg/watir/
This is a good time for me to talk about a couple of things we get with
Subversion.
1. Every commit gets a global commit number, which effectively amounts to a
tag. What this means is that we can now reliably identify any development
version that you pull out of SVN (in case we have trouble reproducing a bug or
whatever). This in fact will be reported in Watir::IE::VERSION, e.g.:
1.5.0.926. The last number is the SVN revision number, uniquely identifying a
snapshot of the entire code base (not just the watir.rb file).
2. File history is retained when files are renamed or moved. This didn't happen
with CVS and so we were reluctant to rename files or reorganize the code. Now
there is little reason not to do that.
BTW, there has been some confusion about what it means to "check out"
code from CVS or SVN. Unlike other source control systems, neither CVS nor SVN
allow or support locking files. So anyone can check out files. But these
systems have checks in place that check to see if anyone has modified any of
the files you are checking in since you checked them out. If so, you will have
to merge your changes with theirs.
Wiki
We are migrating the wiki to the Confluence wiki on OpenQA. I've
started the process, but there is still plenty of work to be done.
http://wiki.openqa.org/display/WTR
The main advantages of Confluence over what we've used before is that it allows
attachments so it will be easy to set up contributions pages and allow people
with small libraries or example code or whatever to easily share it with
others. We will probably be moving some of the unsupported contributions that
we've previously packaged with Watir to the wiki. (So that only supported code
will be contained in our library).
Any Watir users can have access to this wiki. Unlike past wiki's, you do need
an account first. (This should keep the wiki spammers away.)
Tracking
I've just started to set up the new bug tracking system. This is
Jira, which is really good. The main problem with the old tracker at RubyForge
was that you couldn't reclassify bugs as features etc. Jira lets you mix them
all together in a single system. You can check this out here.
http://jira.openqa.org/browse/WTR?report=com.atlassian.jira.plugin.system.project:roadmap-panel
Another good thing about Jira is that it allows people to vote on the features and
fixes that they want most. If there is a bug that you want fixed, feel free to
put it in Jira.
Bret
|
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
