That sounds great, I've gotten involved just barely with SafariWatir, but it's well behind what I'd consider moving into the core. As we go forward with various implementations, we should be tracking against watir spec to certify and pull in until we get to Watir 2.0, where we're also still using it but in a different sense.
-c On Wed, Nov 25, 2009 at 5:48 PM, Bret Pettichord <[email protected]>wrote: > Hey, I've been working in Jira today, and I'm worried that we'll need to > change things around a bit. > > I see that we now have the ChromeWatir and SafariWatir bug reports in the > Watir project. I think these need to be set up as separate projects on > OpenQA. > > This is how the Selenium projects are set up. > http://jira.openqa.org/secure/BrowseProjects.jspa > > The reason is that in Jira, a project is considered to be a series of > releases based on a common code base. We added the FireWatir tickets to the > project when we merged the Watir and FireWatir codebases. > > But SafariWatir and ChromeWatir are still managed as separate code bases > with separate release schedules. I know of no plans to change this. > > I noticed this when I was updating the Watir Jira Project to include our > latest releases. > http://jira.openqa.org/secure/project/ManageVersions.jspa?pid=10080 > > Each release has a release number and date, but clearly these will be > different for these other Watir projects, so they need to be hosted in > separate OpenQA projects. > > Does this make sense? > > Bret > > -- > Bret Pettichord > Lead Developer, Watir, www.watir.com > > Blog, www.io.com/~wazmo/blog <http://www.io.com/%7Ewazmo/blog> > Twitter, www.twitter.com/bpettichord > > > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
