[vtk-developers] VTK code review / testing / integration workflow

[Berk Geveci]

Hi guys,

To close the loop on the tool side of things, we will be evaluating Gitlab
for another project at Kitware. After that, I'll revive the tool
discussion. From what I heard so far, it sounds like we will settle on
Github or Gitlab (or something similar).

Best,
-berk



On Thu, Sep 4, 2014 at 10:31 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

>
> On Sat, Aug 23, 2014 at 9:04 PM, David Thompson <
> david.thompson at kitware.com> wrote:
>
>> <snip>
>> - It would be nice to have tighter integration with the release process
>> and issue tracking so that reports of features added and bugs fixed could be
>
>
> +1
>
> The bugtracker is only loosely integrated into the process. I'ld like it
> to be tighter too so that hopefully the number of bugs in the tracker will
> be limited and always recent.
>
>
>
>> generated. I think what we do of that is mostly by hand now, isn't it?
>>
>>
> Yes mostly by hand.
>
> * before a release we scan the bug tracker and try to address the most
> important reports.
>
> * during the release candidate cycle I use the bug tracker and the "found
> in" "fixed in" fields to keep track of the bugs that need to be fixed
> before the final release
>
> We keep track of what changed in the release entirely outside of the bug
> tracker.
>
> * I send an email to all authors and ask them to summarize their changes
>  to make up the release notes so we know overall what happened.
>
> * Then I run $VTKSRC//Utilities/Maintenance/sematicDiffVersion.py to make
> the API diff report so that we have a list of the added / newly legacy'd /
>  and removed items.
> See: http://www.vtk.org/Wiki/VTK/API_Changes_6_0_0_to_6_1_0
>
>
>
>
>
>
>
>> Suggested Requirements:-)
>>
>> - Review system comments should be Markdown or rST or something easily
>> presented as HTML which can include links -- at least to the VTK wiki and
>> bug tracker, if nothing else. It would be really nice if pull requests
>> could effectively become parts of a wiki page or blog so that we could
>> curate user-guide-style documentation instead of just doxygen reference
>> docs. Not that every topic would have to become part of a user's guide, but
>> it should be easy to pull topic info into a user's guide.
>>
>> - An anti-requirement: Less e-mail spam when (1) a topic includes
>> multiple commits and/or (2) automated testing completes. For instance, I
>> can think of one topic I'm a reviewer on that has 40-something commits.
>> There are 16 changesets and reviewers get 1 per commit per
>> changeset-the-commit-is-modified.
>>
>>         2¢,
>>         David
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20140905/e284596a/attachment-0002.html>