About the versioning. I'd suggest to use semantic versioning ( http://semver.org) from now on. It just makes sense and would be nice to adhere to some rules and let the world know that we are adhering to them.
Also, wouldn't that be a nightmare if we'd support and develop multiple versions of Watir (e.g. fixing only bugs in 1.6)? It would make sense if, let's say Jari's Watir-WebDriver would be the next *official* version of Watir. In that case there would be 2 completely different codebases which should be developed separately, e.g. fix only bugs in the *old* one and add new functionality to the new one. Why would you want to make 1.6 as so special? Makes sense? Why not be more agile and release when it seems that we've fixed some critical bugs and/or added valuable new features? I don't see how "release plans", which should be filled, help us to get into rapid release cycle. Check out RSpec for example, where releases happen almost every week or even few days in a row. Why not take that route also if it's possible? Of course plans for future development would make sense, e.g. what should be done, what should not be done and so on, but specific plans about "does this belong to the next release or not" doesn't make much of a sense in my opinion. Jarmo On Sat, Dec 18, 2010 at 1:05 AM, Bret Pettichord <[email protected]>wrote: > I would like us to put the 1.6.x branch into maintenance,. which means we > would only fix bugs in it. > > The new work would be in a 1.7.x branch. > > I've been in touch with Charley just a bit recently. Personally I was > thinking we should have a release manager for each release to help > coordinate what was and wasn't in scope for the release (and would release > the gems when the release was complete.) It would probably be two different > people. > > I've been collecting notes for a while on what I thought would be in each, > and was planning on putting these on the wiki so we could discuss. I hope to > get this done next week; if not then, then next week. I am off from work > until Jan 3, so have some free time to work on this. > > If you want to get the ball rolling, you could start by making a wiki page > with a release contents proposal. > > Thanks for taking the initiative to bring this up and offer to be the gem > owner. > > I also have several Jira tickets than I've been meaning to follow up on. > Hopefully will find the time over the holiday break. > > Bret > > On Fri, Dec 17, 2010 at 12:57 PM, Jarmo <[email protected]> wrote: > >> Hi! >> >> I've been trying to contact Charley on the IRC now for about a week. I >> wanted to ask his thoughts about releasing new version of Watir, which >> includes some quite critical bugfixes and wanted to ask how did his venture >> with removing activesupport dependenfy from firewatir go? But Charley hasn't >> been available on IRC for some reason. I'm not saying that he has to be, but >> this is life and these things are expected. >> >> That's when i remembered that here was some time ago sent e-mails about >> who should the gem owners be and such. I'd like to get owner rights so i >> could make the gem pushes myself if it's okay with everyone else, of course. >> >> So, what do you think about releasing new version of Watir and granting me >> access to make gem pushes if the time is right? >> >> Jarmo >> >> _______________________________________________ >> Wtr-development mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/wtr-development >> > > > > -- > Bret Pettichord > Lead Developer, Watir, www.watir.com > > Blog, www.io.com/~wazmo/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
