Patches, issue-tracking, maintenance etc.

Ucan, Emre (ADITG/ESB) eucan at de.adit-jv.com
Wed Jun 14 07:04:17 EDT 2017


Hello Gunnar,

My answers are below:

Best regards

Emre Ucan
Engineering Software Base (ADITG/ESB)

Tel. +49 5121 49 6937

> -----Original Message-----
> From: Gunnar Andersson [mailto:gunnar.genivi at gmail.com]
> Sent: Dienstag, 13. Juni 2017 18:08
> To: Ucan, Emre (ADITG/ESB); genivi-ivi-layer-management at lists.genivi.org
> Cc: Jeremiah Foster
> Subject: Re: Patches, issue-tracking, maintenance etc.
> 
> 
> Hello Emre
> 
> On Tue, 2017-06-13 at 11:22 +0000, Ucan, Emre (ADITG/ESB) wrote:
> > Hello Gunnar,
> >
> > Wayland-ivi-extension 1.13 requires weston 2.0. Therefore, we have to
> > update both together.
> > 1.13 version is backwards compatible with 1.11. I will send an email to
> > BIT team for updating to new versions.
> 
> That's fine.  GDP will pick up this change via the meta-ivi most likely,
> assuming that we can get an early dev branch to work on quite soon.
> 
> >
> > Recently, we introduced a new protocol. Therefore, we want to update
> > compliance for the upcoming release.
> > The upcoming version would be 2.0, because we made backwards
> incompatible
> > changes.
> 
> OK.  So GDP main HMI needs to change some things also I assume?  Will you
> able to support that activity and help us explain what needs to be done?
> 
> >
> > For issue tracking and patches , best way for us would be to use github.
> 
> Sure, but the Issues are turned off on the GitHub repository, so I don't see
> how you're doing it.  :-)
> 
> Looping in Jeremiah into the thread, but generally I would say the GENIVI
> strategy is to let component maintainers decide on their preferred tooling,
> and only provide some defaults (JIRA/Confluence and other) if there are no
> special requests.
> 
> But in that case it needs to be really well documented so that people going
> to the most common place will find their way, so let's try to do that.
> 
> So you prefer to enable the GitHub issues on the repository then?
> I have the possibility to do it - just want to loop in our community manager
> also.
> 
> When we have done it, will you consider documenting it in the project
> README
> also?

Yes we can do.
> 
> Finally, since we're waiting for the issue tracker... I requested
> specifically a maintenance branch for 1.11 with the critical bugfix (or
> bugfixes) - what do you think about it?

Yes, we can do. But we have to wait for Eugen (maintainer).  He will return next week.
Actually, we asked Jeremiah to enable write access also to me, so that I can push patches when Eugen is not available. But Jeremiah did not reply yet for our request.

> 
> Thanks,
> - Gunnar
> 
> 
> >
> > Best regards
> >
> > Emre Ucan
> > Engineering Software Base (ADITG/ESB)
> >
> > Tel. +49 5121 49 6937
> >
> > > -----Original Message-----
> > > From: genivi-ivi-layer-management [mailto:genivi-ivi-layer-management-
> > > bounces at lists.genivi.org] On Behalf Of Gunnar Andersson
> > > Sent: Montag, 12. Juni 2017 18:25
> > > To: genivi-ivi-layer-management at lists.genivi.org
> > > Subject: Patches, issue-tracking, maintenance etc.
> > >
> > >
> > > Hello Layer Managers...
> > >
> > > The Chromium work triggers a crashing bug which was fixed by this patch:
> > > https://git.io/vH9Ls (wayland-ivi-extension)
> > >
> > > So we got this proposed for chromium recipes:
> > >
> > > https://git.io/vH9LV (meta-genivi-dev)
> > >
> > > Everyone basically agrees we don't want to carry stuff like that around
> > > in GDP yocto layers if we can avoid it - especially not for something
> > > that is fixed in the main project
> > >
> > > But GDP is currently on 1.11.0 of wayland-ivi-extensions.  It should
> > > probably update to 1.13 in the next phase but it takes some time.  (Or
> > > what
> > > is your guidance?  What incompatibility can be expected?  Are you, or
> > > have
> > > you considered strict semantic versioning?)
> > >
> > > I wanted therefore to propose to backport this important bugfix, and
> > > maybe if you have done some other important bugfixes which will not
> > > change any compatibility.  Would you consider doing that and keep a
> > > temporary maintenance branch for 1.11?  What do you think?
> > >
> > > (There is no 1.12, right?  Or I did not see the tag).
> > >
> > > Then, process related:  I started looking at how to ask for this, with
> > > issue trackers and such.  The README does not direct anyone to a bug
> > > tracker, or any other info about how to work in the open-source project.
> > >
> > > Good practice says I should easily find that there.  I did not find an
> > > immediate link in the Wiki pages [1] either - can you try to link
> > > together the pages with the code in a better way?  (And the Wiki pages
> > > are also missing reference to an issue/bug tracker isn't it?)
> > >
> > > Should I make the request on JIRA [2]?  That tracker is almost empty.
> > > There's clearly active development going on, but are you not tracking
> > > any issues?  Is it all done through the mailing list or are there other
> > > methods?
> > >
> > > By the way - the mail archive [3] is broken and is missing several
> > > months of emails (did no-one notice?).  I already sent a message to the
> > > genivi-devops list to notify about it, so hopefully that will be fixed.
> > >
> > > Thanks for considering my questions, both the details on code, and
> > > general
> > > on process.
> > >
> > > Sincerely,
> > > - Gunnar
> > >
> > > [1]
> > >
> https://at.projects.genivi.org/wiki/display/WIE/Wayland+IVI+Extension+Ho
> > > me
> > > [2] https://at.projects.genivi.org/jira/projects/LM/
> > > [3] http://lists.genivi.org/pipermail/genivi-ivi-layer-management/
> > >
> > > --
> > > Gunnar Andersson <gandersson at genivi.org>
> > > Development Lead
> > > GENIVI Alliance
> > >
> > >
> > > _______________________________________________
> > > genivi-ivi-layer-management mailing list
> > > genivi-ivi-layer-management at lists.genivi.org
> > > http://lists.genivi.org/mailman/listinfo/genivi-ivi-layer-management



More information about the genivi-ivi-layer-management mailing list