Changelog for 0.2.5

[Jason Filby]

Hi all

For the new changelog, I'd like to do away with the mere compilation
of commit messages. Firstly because it takes forever for one person to
do this and secondly because it doesn't mean much to people following
the project.

Could everyone write down their changes in a way meaningful to a
technical end-user (that has no knowledge of our codebase) on the Wiki
here:
http://mok.lvcm.com/cgi-bin/reactos/roswiki?ChangeLog-0.2.5

Cheers
Jason

[Alex Ionescu]

Jason Filby wrote:
> Hi all
>
> For the new changelog, I'd like to do away with the mere compilation
> of commit messages. Firstly because it takes forever for one person to
> do this and secondly because it doesn't mean much to people following
> the project.
>
> Could everyone write down their changes in a way meaningful to a
> technical end-user (that has no knowledge of our codebase) on the Wiki
> here:
> http://mok.lvcm.com/cgi-bin/reactos/roswiki?ChangeLog-0.2.5
>
> Cheers
> Jason
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

So there is going to be a 0.2.5?

It would be nice to have talked about it on the ML.

Best regards,
Alex Ionescu

[Gregor Anich]

Alex Ionescu wrote:
> Jason Filby wrote:
> > Hi all
> >
> > For the new changelog, I'd like to do away with the mere compilation
> > of commit messages. Firstly because it takes forever for one person to
> > do this and secondly because it doesn't mean much to people following
> > the project.
> >
> > Could everyone write down their changes in a way meaningful to a
> > technical end-user (that has no knowledge of our codebase) on the Wiki
> > here:
> > http://mok.lvcm.com/cgi-bin/reactos/roswiki?ChangeLog-0.2.5
> >
> > Cheers
> > Jason
>
> So there is going to be a 0.2.5?
>
> It would be nice to have talked about it on the ML.
>
> Best regards,
> Alex Ionescu

Hi!

Why not release 0.2.5 if there is not gonna be 0.3.0 this year?
IMO we could have released 0.2.5 already sometime ago.

- blight

[Richard Campbell]

How about...christmas for a release date of 0.2.5?  Bad idea you say?  
Everyone will be home...reading slashdot and other sites... :)

Gregor Anich wrote:
> Alex Ionescu wrote:
> > Jason Filby wrote:
> > > Hi all
> > >
> > > For the new changelog, I'd like to do away with the mere compilation
> > > of commit messages. Firstly because it takes forever for one person to
> > > do this and secondly because it doesn't mean much to people following
> > > the project.
> > >
> > > Could everyone write down their changes in a way meaningful to a
> > > technical end-user (that has no knowledge of our codebase) on the Wiki
> > > here:
> > > http://mok.lvcm.com/cgi-bin/reactos/roswiki?ChangeLog-0.2.5
> > >
> > > Cheers
> > > Jason
> >
> > So there is going to be a 0.2.5?
> >
> > It would be nice to have talked about it on the ML.
> >
> > Best regards,
> > Alex Ionescu
>
> Hi!
>
> Why not release 0.2.5 if there is not gonna be 0.3.0 this year?
> IMO we could have released 0.2.5 already sometime ago.
> blight
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Steven Edwards]

Hi,

--- Richard Campbell [e-mail] wrote:
> How about...christmas for a release date of 0.2.5?  Bad idea you say?  
> Everyone will be home...reading slashdot and other sites... :)

I pitched the topic on IRC a few days ago and it was a even split on if we should do a 0.2.5 or
not. For the record I am in favor of doing the release. I think Jason made the call and its a good
one. We have put off a release for far too long and networking will not be stable for at least
another month. Having a new release will attract some attention and help make things a little more
stable. We can't keep telling people to download nightly builds that may or may not boot.

Thanks
Steven

__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250

[James Tabor]

Hi Jason,
This list looks very weak, I thought there are more changes made in the
last three months. There should be more!
James

Jason Filby wrote:
> Hi all
>
> For the new changelog, I'd like to do away with the mere compilation
> of commit messages. Firstly because it takes forever for one person to
> do this and secondly because it doesn't mean much to people following
> the project.
>
> Could everyone write down their changes in a way meaningful to a
> technical end-user (that has no knowledge of our codebase) on the Wiki
> here:
> http://mok.lvcm.com/cgi-bin/reactos/roswiki?ChangeLog-0.2.5
>
> Cheers
> Jason

[Jason Filby]

Hi James

Then add them! It's not my responsibility to compile the list anymore;
it's the responsibility of every developer that made a change - and
wants to see that change in the changelog.

I've tried trawling through the commit list up until the release
before last (I think it was); but I can't scale to the extent of going
through the amount of messages we have these days between releases --
finding comments that say something meaningful and trying to present
one style of informative writing. It's just too much for one person.

Cheers
Jason

On Thu, 16 Dec 2004 01:57:18 +0000, James Tabor
[e-mail] wrote:
> Hi Jason,
> This list looks very weak, I thought there are more changes made in the
> last three months. There should be more!
> James

[Casper Hornstrup]

Is there an interrest in generating a draft version of the ChangeLog automatically from the commit logs?
Eg. If you commit with the following commit message:

Add notepad to the bootcd

@changelog Included Notepad on the bootable CD

"Included Notepad on the bootable CD" will be added to the ChangeLog. The ChangeLog could be made avaialble via RSS.

The problem I'm trying to solve is that if you generate the ChangeLog before the release, you need to go through all commit messages
to find the important ones. When you commit a particular change you know if it is important enough to include in the ChangeLog.

Casper
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Jason Filby
> Sent: 16. december 2004 13:27
> To: ReactOS Development List
> Subject: Re: [ros-dev] Changelog for 0.2.5
>
> Hi James
>
> Then add them! It's not my responsibility to compile the list 
> anymore; it's the responsibility of every developer that made 
> a change - and wants to see that change in the changelog.
>
> I've tried trawling through the commit list up until the 
> release before last (I think it was); but I can't scale to 
> the extent of going through the amount of messages we have 
> these days between releases -- finding comments that say 
> something meaningful and trying to present one style of 
> informative writing. It's just too much for one person.
>
> Cheers
> Jason
>
> On Thu, 16 Dec 2004 01:57:18 +0000, James Tabor 
> [e-mail] wrote:
> > Hi Jason,
> > This list looks very weak, I thought there are more changes made in 
> > the last three months. There should be more!
> > James
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Jason Filby]

Hi Casper

On Thu, 16 Dec 2004 13:51:57 +0100, Casper Hornstrup
[e-mail] wrote:
> Is there an interrest in generating a draft version of the ChangeLog automatically from the commit logs?

The issue is that several commits can contribute towards what would be
one message in the changelog, if they make up parts of an objective.
But I'm still open to this idea if developers are willing to work with
such a system.

Cheers
Jason

[Patrick Mauritz]

Am Donnerstag, 16. Dezember 2004 13:51 schrieb Casper Hornstrup:
> The problem I'm trying to solve is that if you generate the ChangeLog
> before the release, you need to go through all commit messages to find the
> important ones. When you commit a particular change you know if it is
> important enough to include in the ChangeLog.

as a variation to this, add a file to the tree, "ChangeLog" (or even 
"ReleaseNotes", for something more highlevel) and add comments to this as you 
go like you would in the commit message

less clutter in the commit logs and all information is in a single spot. with 
each release, either clear the file or add some header to separate released 
information from new one as part of release engineering.

eg.

= current =
* done this (gvg)
* done that (ekohl)
* completed something else (sedwards)

= 0.2.5 (released 2004-12-24) =
...

patrick mauritz
-- 
Besides a mathematical inclination, an exceptionally good mastery of 
one's native tongue is the most vital asset of a competent programmer.

[James Tabor]

Hi!
Jason Filby wrote:
> Hi James
>
> Then add them! It's not my responsibility to compile the list anymore;
> it's the responsibility of every developer that made a change - and
> wants to see that change in the changelog.

AAAH! Duck and cover! Okay!
> I've tried trawling through the commit list up until the release
> before last (I think it was); but I can't scale to the extent of going
> through the amount of messages we have these days between releases --
> finding comments that say something meaningful and trying to present
> one style of informative writing. It's just too much for one person.
>
> Cheers
> Jason

Haven fun with high energy physic,
James

[Jason Filby]

Hi James

Hehe, I didn't mean that to be as rude as it now reads ;) Sorry about that!

Cheers
Jason

On Thu, 16 Dec 2004 13:10:17 +0000, James Tabor
[e-mail] wrote:
> > Then add them! It's not my responsibility to compile the list anymore;
> > it's the responsibility of every developer that made a change - and
> > wants to see that change in the changelog.
>
> AAAH! Duck and cover! Okay!

[James Tabor]

HI!
We use the same password or did our account info change?
Thanks,
James

Jason Filby wrote:
> Hi all
>
> For the new changelog, I'd like to do away with the mere compilation
> of commit messages. Firstly because it takes forever for one person to
> do this and secondly because it doesn't mean much to people following
> the project.
>
> Could everyone write down their changes in a way meaningful to a
> technical end-user (that has no knowledge of our codebase) on the Wiki
> here:
> http://mok.lvcm.com/cgi-bin/reactos/roswiki?ChangeLog-0.2.5
>
> Cheers
> Jason