On Tue, Nov 03, 2020 at 11:11:48 +0100, Andrea Bolognani wrote:
> On Mon, 2020-11-02 at 19:35 +0100, Jiri Denemark wrote:
> > On Mon, Nov 02, 2020 at 12:09:13 +0100, Andrea Bolognani wrote:
> > > On Mon, 2020-11-02 at 11:20 +0100, Jiri Denemark wrote:
> > > [...]
> > > > * Improvements
> > > >
> > > > * Bug fixes
> > >
> > > It would have been nice if you had removed the empty "Improvement"
> > > section at the same time as you updated the release date... Can you
> > > please look for such empty sections and deal with them next time?
> >
> > OK, it should not happen anymore thanks to the following write-only sed
> > command integrated into my release script :-)
> >
> > sed -ne '/^[^ ]/{x; s/^\* [^\n]*\n\+$//; /^$/!p; ${x; p}; d}; H' NEWS.rst
>
> Wow, that *is* write-only :D
>
> Would it make sense to include the release script in the git
> repository? libosinfo and friends already have something along those
> lines, though I'm unclear on the scope of your specific take on it.
I don't mind publishing it, but...
- it's very tied to my environment and the way I do this kind of things
(interactive, requiring confirmations with a possibility to manually
change things before continuing with the next step)
- it's in bash
- it does both libvirt and libvirt-python at once
- when I need to change something I usually need to do it immediately to
be able to make the release, i.e., with no review
- I don't fancy random people messing with the script without my control
:-)
That said, libvirt.git is definitely not the right repo for it. But I
guess my personal repo could work.
Jirka
