>> ------ Developer Responsibilities, aka What You Need To Do NOW ------ >> >> 1. Start using the Mercurial-enabled SUNWonbld tools to manage your >> Teamware workspaces. >> >> 2. For bonus points, read the Mercurial book: http://hgbook.red-bean.com/ >> >> 3. That's about it. > > I was hoping to see a "3. To save yourself some last-minute pain, > convert your teamware onnv child to mercurial at some point between now > and August 4th. Here's how.". I don't see that here nor on the SCM > project page (or maybe I'm not looking in the right place). > > I know that projects have mercurial project workspaces today, and > they'll sure be sitting pretty when the August 4th flag day rolls > around. It would be good to encourage others to do the same so that you > don't have hundreds of people flailing around all at once on flag day. > Are there instructions and/or helper scripts to assist with this? The > projects who do wait until August 4th will surely need these anyway, > right?
Yep, and thanks for the forward-thinking sentiment. It's a refreshing change to the "I'm just going to wait until I have no choice, and complain about the effect on my project" attitude... > Maybe that's the "more to come" that Mark is referring to under > "Documentation". If so, then never mind. :-) It's the "wx2hg" script. It's part of the tools, and there's a decent manpage. But being more explicit about how to go about this is definitely in the works. There are too many people to hold all the hands, but we're definitely giving y'all something to hold on to. --Mark
