Re: [Wireshark-dev] Review of Gerrit patch for RTPS

It makes sense. I will create a bug and attach a capture to it. Then I will reference the bug from the Gerrit issue. That is the process right? Thanks, Juanjo Martin On Thu, Nov 19, 2015 at 9:14 AM, Dario Lombardo wrote: > I think that attaching some samples would

Re: [Wireshark-dev] Review of Gerrit patch for RTPS

2015-11-19 11:28 GMT+01:00 Juan Jose Martin Carrascosa : > It makes sense. I will create a bug and attach a capture to it. Then I > will reference the bug from the Gerrit issue. That is the process right? > yes exactly. > > Thanks, > Juanjo Martin > > On Thu, Nov 19, 2015 at

Re: [Wireshark-dev] Release process: Transifex Sync

> > > I agree with you. There is need to sync with Transifex as one of > latest step of releasing. > I was conviced that Alexis put the sync in place. Doesn't it work? https://www.wireshark.org/lists/wireshark-dev/201502/msg00162.html

Re: [Wireshark-dev] Review of Gerrit patch for RTPS

I think that attaching some samples would help a lot. On Wed, Nov 18, 2015 at 7:21 PM, Juan Jose Martin Carrascosa wrote: > I assumed that you were busy. Thanks for the answer. > > Is there anything I can help with? I may be able to spend some hours this > weekend. > > Thanks,

[Wireshark-dev] Release process: Transifex Sync

Hi, First of all a huge Thank you to all the developers for a gorgeous 2.0.0 release! I saw that the language files haven't been updated before building 2.0.0. Therefore the latest translations like 'Next Packet in Conversation' and my fixes for the keyboard shortcuts in the German translation

Re: [Wireshark-dev] Release process: Transifex Sync

On 19 November 2015 at 09:22, Uli Heilmeier wrote: > that the language files haven't been updated before building 2.0.0. > Therefore the latest translations like 'Next Packet in Conversation' and my > fixes for the keyboard shortcuts in the German translation are missing. > >

Re: [Wireshark-dev] Release process: Transifex Sync

Hi, There is sync every week (With other stuff like manuf...) I have ask the release manager to also sync translation before a release... (but look missing for 2.0.0) Yes, we need also work on "process" for update translation.. (like frozen, mailing...) Regards, On Thu, Nov 19, 2015 at 9:40

[Wireshark-dev] Is it better to have dissected and lost than never to have dissected at all?

This question has probably been asked before, so I thought I'd at least put a Tennyson twist on it. I started getting more serious about converting dissectors to the "new style". I submitted a bunch of patches where it was obvious that the dissectors fell into the "give me everything"

[Wireshark-dev] Buildbots

I've found 2 different buildbot projects for wireshark https://buildbot.wireshark.org/petri-dish/ and https://buildbot.wireshark.org/wireshark-master/ Can anyone explain me the difference? I've understood that petri-dish is manually triggered by core-devs from gerrit. Who triggers the

Re: [Wireshark-dev] Buildbots

As you said, petri-dish is triggered by core devs for unmerged gerrit changes to test them before merging. Master is triggered on every merge to build the actual git master branch. On Thu, Nov 19, 2015 at 11:45 AM, Dario Lombardo < dario.lombardo...@gmail.com> wrote: > I've found 2 different

Re: [Wireshark-dev] Buildbots

There's also the: 2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfall 1.12 buildbot - https://buildbot.wireshark.org/wireshark-1.12/waterfall Debian LTS buildbot - https://buildbot.wireshark.org/wireshark-lts/waterfall These are all listed on the develop page -