On Thu, 2017-01-05 at 16:45 +0100, Andrea Bolognani wrote: > > This avoids the need to rely on magic markers being the in > > intermediate text file, which could get mis-interpreted > > depending on what people write in the release notes. > > The only case where that would happen would be if someone > started a change description with one of the markers, which > I think you'll agree is very unlikely to actually happen. > > But if you think we should prevent it altogether, it's > fairly simple to tweak the script and add a marker in front > of the change description in the XSLT, and strip it later > in the Python code so that it doesn't ultimately show up in > the NEWS file. Implementing this idea actually allowed me to shave ~10 lines off the Python script :) Do you still have concerns not addressed by my replies or are you okay with me going ahead with this? As I mentioned earlier, I'd like to avoid having this on the list for too long: 3.0.0 is not very far away, so it's about time to get the release notes into shape and I'd prefer using the new source format right away instead of having to convert later. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
