On 09/12/11 03:33, David Seikel wrote:
> All the information should still stay with the source code. Making
> people chase info all over the web wont help.
Copy the blog into the NEWS file then, making the developers copy paste
all over the place isn't nice either. Furthermore, you gotta ask
your
On Fri, 9 Dec 2011 10:08:10 +0900 Daniel Juyung Seo
wrote:
> On Fri, Dec 9, 2011 at 1:29 AM, Tom Hacohen
> wrote:
> > What I said in IRC:
> >
> > In my POV, we should ditch the NEWS file entirely and change the
> > way we handle the Changelog.
> >
> > Honestly, NEWS file was for the time before
On Fri, Dec 9, 2011 at 1:29 AM, Tom Hacohen
wrote:
> What I said in IRC:
>
> In my POV, we should ditch the NEWS file entirely and change the way we
> handle the Changelog.
>
> Honestly, NEWS file was for the time before people tweeted, blogged, and
> what not. It's not really relevant anymore, no
What I said in IRC:
In my POV, we should ditch the NEWS file entirely and change the way we
handle the Changelog.
Honestly, NEWS file was for the time before people tweeted, blogged, and
what not. It's not really relevant anymore, not in the way we use it anyway.
Changelog: we should add one e
On 08/12/11 15:25, Vincent Torri wrote:
> Hey
>
> imho, NEWS fileshave too much entries. A NEWS file should only mention
> API additions and improvements. Eventually, big bugs or regressions
> that have been fixed should go there too. NEWS should focus on
> important things, not minor ones. ChangeL
