On Fri, 2016-10-21 at 10:32 +0100, Daniel P. Berrange wrote:
> Take a look at how we structure NEWS file for gtk-vnc:
>
> https://git.gnome.org/browse/gtk-vnc/tree/NEWS
>
> We try to give users concise information, ordered by importance
>
> That is the kind of format I think we should aim
On Fri, Oct 21, 2016 at 12:33:44PM +0200, Sławek Kapłoński wrote:
> Hello,
>
> I'm quite new in libvirt community so I don't know all requirements
> which community have but did You know about reno project from Openstack:
> http://docs.openstack.org/developer/reno/ ? It's used for managing
>
Hello,
I'm quite new in libvirt community so I don't know all requirements
which community have but did You know about reno project from Openstack:
http://docs.openstack.org/developer/reno/ ? It's used for managing
releae notes which are added in git as separate files. Maybe it can be
some
On Fri, Oct 21, 2016 at 10:10:50AM +0800, Michal Privoznik wrote:
> On 19.10.2016 19:58, Daniel P. Berrange wrote:
> > On Wed, Oct 19, 2016 at 01:53:41PM +0200, Andrea Bolognani wrote:
> >> Hi,
> >>
> >>
> >
> > Why don't we simply have a NEWS file in GIT, and require that
> > non-trivial
On Wed, 2016-10-19 at 18:22 -0400, John Ferlan wrote:
> I really think we should do something - especially to be able to
> describe what's new, what was added when, etc. beyond what DV culls out
> of the existing commits.
>
> Whether the mechanism is some news.html.in or features.html.in or
>
On 19.10.2016 19:58, Daniel P. Berrange wrote:
> On Wed, Oct 19, 2016 at 01:53:41PM +0200, Andrea Bolognani wrote:
>> Hi,
>>
>>
>
> Why don't we simply have a NEWS file in GIT, and require that
> non-trivial commits or patch series include an update to NEWS,
> so the NEWS file gets populated at
On Wed, 2016-10-19 at 21:40 +0200, Martin Kletzander wrote:
> > > I understood it like this:
> > >
> > > - stop generating NEWS file
> > > - populate NEWS file with notable features/bug-fixes along with the
> > > changes themselves
> > > - use NEWS to make nice news.html
> >
> > Why
On 10/19/2016 07:53 AM, Andrea Bolognani wrote:
> Hi,
>
> there's an idea that has been kicking around in my head for
> a while, and I'd like to share it with the list to gather
> some feedback before I forget about it :)
>
> Right now, each entry in our NEWS file contains what is
> basically
On Wed, Oct 19, 2016 at 03:59:37PM +0200, Andrea Bolognani wrote:
On Wed, 2016-10-19 at 15:19 +0200, Martin Kletzander wrote:
> > Why don't we simply have a NEWS file in GIT, and require that
> > non-trivial commits or patch series include an update to NEWS,
> > so the NEWS file gets populated
On Wed, 2016-10-19 at 15:19 +0200, Martin Kletzander wrote:
> > > Why don't we simply have a NEWS file in GIT, and require that
> > > non-trivial commits or patch series include an update to NEWS,
> > > so the NEWS file gets populated at time the feature/bug fix
> > > gets merged.
> >
> > I'm
On Wed, Oct 19, 2016 at 02:54:06PM +0200, Andrea Bolognani wrote:
On Wed, 2016-10-19 at 12:58 +0100, Daniel P. Berrange wrote:
Why don't we simply have a NEWS file in GIT, and require that
non-trivial commits or patch series include an update to NEWS,
so the NEWS file gets populated at time the
On Wed, Oct 19, 2016 at 12:58:55PM +0100, Daniel P. Berrange wrote:
On Wed, Oct 19, 2016 at 01:53:41PM +0200, Andrea Bolognani wrote:
Hi,
there's an idea that has been kicking around in my head for
a while, and I'd like to share it with the list to gather
some feedback before I forget about it
On Wed, 2016-10-19 at 12:58 +0100, Daniel P. Berrange wrote:
> Why don't we simply have a NEWS file in GIT, and require that
> non-trivial commits or patch series include an update to NEWS,
> so the NEWS file gets populated at time the feature/bug fix
> gets merged.
I'm strongly against adding
On Wed, Oct 19, 2016 at 01:53:41PM +0200, Andrea Bolognani wrote:
> Hi,
>
> there's an idea that has been kicking around in my head for
> a while, and I'd like to share it with the list to gather
> some feedback before I forget about it :)
>
> Right now, each entry in our NEWS file contains what
14 matches
Mail list logo
