Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Fw: New release notes engine and how this affects your workflow

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912

----- Forwarded by Kenneth Hussey/Ottawa/IBM on 11/30/2006 11:28 AM -----
Neil Skrypuch/Toronto/IBM

11/30/2006 10:42 AM

Ed Merks/Toronto/IBM@IBMCA, Nick Boldt/Toronto/IBM@IBMCA, Dave Steinberg/Toronto/IBM@IBMCA, Marcelo Paternostro/Toronto/IBM@IBMCA, Dmitry Denisov/Toronto/IBM@IBMCA, Kenneth Hussey/Ottawa/IBM@IBMCA, Lei L Zhang/China/IBM@IBMCN, Paul Elder/Ottawa/IBM@IBMCA, Christian Damus/Ottawa/IBM@IBMCA, mtaal@xxxxxxxxx, stepper@xxxxxxxxxx, jcheuoua@xxxxxxxxx
New release notes engine and how this affects your workflow

The new release notes engine that I've built is now up and has replaced the old engine.

The left nav for EMF and MDT has been updated accordingly, the EMFT nav has a patch that Nick can commit when he gets in, but here's some direct links:

One of the benefits of this new engine is that you shouldn't need to create duplicate bugs for the maintenance stream anymore, simply tag the commit to HEAD and to Rx_y_maintenance with the same bug id, and the new release notes will sort things out based on where it was commited to in CVS. For example:

Another benefit of the engine is that you can now see the release notes for a specific build rather than just an entire release cycle, for example:

Overall, the release notes should be more accurate (less duplicates, branch crossing, etc), faster, and less work for committers (and website maintainers) now.

Nick: Could you pass this along to anyone from MDT.* and EMFT.* that I missed?

- Neil

Back to the top