Re: [ros-dev] Improving our procedure

[Ged Murphy]

I agree, but something is obviously amiss somewhere as changelogs aren't
being done.
Considering you can't force people to do them, maybe making it easier would
help?

I don't know what else to suggest, nagging people doesn't work as Z98 will
confirm.
Maybe we just need to put more emphasis on getting it done and gradually
slide people back into that way of working?

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Alex Ionescu
Sent: 15 December 2009 17:45
To: ReactOS Development List
Subject: Re: [ros-dev] Improving our procedure

I still don't see how writing such a webservice + figuring out how to use it
is simpler than just dumping your user log and copy/pasting the entries with
a little bit of formatting cleanup.

It never took me more than an hour, tops, for hundreds of commits in a given
release!

I don't understand how a ReactOS developer, which (at least I fucking hope
so) probably spends 6 hours debugging an issue by looking at prints,
stepping through code, and finally discovering the race condition (the most
BORING work ever) at least once a week, can't afford doing one hour of
boring work every 6 months?!
Just how lazy are you...

On 2009-12-15, at 12:24 PM, Ged Murphy wrote:
> I definitely like this idea. It's much more workable than a blind script,
> changelogs _need_ human interaction.
> The problem is, who would write such a webservice and would people use it?
>
> Ged.
>
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On
> Behalf Of Timo Kreuzer
> Sent: 15 December 2009 16:45
> To: ReactOS Development List
> Subject: Re: [ros-dev] Improving our procedure
>
> Thinking about the changelog problem, I had the following idea:
>
> On the website there would be a place maybe called "myDevelopment" or
> something. Here you would automatically find a list of all your recent
> commits. Seperated by release version. By default every new commit
> creates a new entry here. But you can manage the entries.
> Edit the message and component of each entry
> Mark an entry as trivial. These changes don't get into the changelog
>
> at all.
> Split an entry, if a single commit contains 2 changes. You can fix up
>
> the messages afterwards.
> Merge 2 or more entries into one new.
>
> On release the whole stuff will be gathered together.
>
> Additional features:
> Mark an entry as active workitem. Folling commits will automatically
>
> go in there.
> Show recent activity on the frontpage.
> Add planned activities, private notes, TODOs, FIXMEs, status, bugzilla
>
> links, etc
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

Best regards,
Alex Ionescu

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev