Date   

Re: Kernel feature support - filesystems and networking

Jan Kiszka
 

On 2017-05-29 04:40, 小口琢夫 / KOGUCHI,TAKUO wrote:
Hi Ben,

Thanks for your efforts.

- overlayfs (CONFIG_OVERLAY_FS)
OVERLAY_FS is one of the features Hitachi wants to use.
I hope you look into this further and I would like to know if other members also want it.
We plan to use this feature with CIP kernels as well.

Regards,
Jan

Best regards,

Takuo Koguchi,
Hitachi, Ltd.


-----Original Message-----
From: cip-dev-bounces@...
[mailto:cip-dev-bounces@...] On Behalf Of Ben Hutchings
Sent: Monday, May 29, 2017 11:13 AM
To: cip-dev@...
Subject: [!][cip-dev] Kernel feature support - filesystems and networking

I apologise for the long delay in responding to the kernel config files I was given. Here's a
first list of features I would like to *not* support. I expect to be able to send additional lists
soon. Let me know if you really need some of the features listed below, and if you have
any ideas about how to mitigate the problems I see.

The following features are enabled in some of the configurations I was sent but seem to
be unsupportable over CIP's time scale:

File systems:
- btrfs (CONFIG_BTRFS_FS)
- Too rapidly changing to backport most fixes
- ceph (CONFIG_CEPH_LIB, CONFIG_CEPH_FS)
- Complex network protocol which is likely to need many fixes
- cifs (CONFIG_CIFS_FS)
- Complex network protocol which is likely to need many fixes
- nfs (CONFIG_NFS_FS, CONFIG_NFSD)
- Complex network protocol which is likely to need many fixes
- ufs (CONFIG_UFS_FS)
- No work by current maintainer for 7 years
- xfs (CONFIG_XFS_FS)
- Maintainers unsupportive of backporting fixes

Networking:
- batman-adv (CONFIG_BATMAN_ADV)
- Rapidly changing
- caif (CONFIG_CAIF)
- No work by current maintainer for 5 years
- dcb (CONFIG_DCB)
- No current maintainer
- hsr (CONFIG_HSR)
- No work by current maintainer for 2 years
- llc2 (CONFIG_LLC2)
- No work by current maintainer for 7 years
- phonet (CONFIG_PHONET)
- Dead protocol
- sctp (CONFIG_IP_SCTP)
- Poor security record
- wimax (CONFIG_WIMAX)
- Dead protocol
- x25 (CONFIG_X25)
- Poor security record

I have some doubts about whether these can be supported:

- ntfs (CONFIG_NTFS_FS)
- Fixes are never marked for stable
- overlayfs (CONFIG_OVERLAY_FS)
- I found many apparently important bug fixes in later kernel
versions that have not been backported

Ben.

--
Ben Hutchings
Software Developer, Codethink Ltd.


_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Re: Kernel feature support - filesystems and networking

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi Ben,

On 29/05/17 03:40, 小口琢夫 / KOGUCHI,TAKUO wrote:
Hi Ben,

Thanks for your efforts.

- overlayfs (CONFIG_OVERLAY_FS)
- I found many apparently important bug fixes in later kernel
versions that have not been backported

Is there a technical reason for these patches not being backported or is it simply that never was requested/needed before?

OVERLAY_FS is one of the features Hitachi wants to use.
I hope you look into this further and I would like to know if other members also want it.
Based on this request, is it possible for you to estimate the effort to do this?

@Takuo is there a kernel developer from Hitachi that would be willing to work under Ben's supervision/review in backporting these patches?

Best Regards

--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Re: Kernel feature support - filesystems and networking

Takuo Koguchi
 

Hi Ben,

Thanks for your efforts.

- overlayfs (CONFIG_OVERLAY_FS)
OVERLAY_FS is one of the features Hitachi wants to use.
I hope you look into this further and I would like to know if other members also want it.

Best regards,

Takuo Koguchi,
Hitachi, Ltd.


-----Original Message-----
From: cip-dev-bounces@...
[mailto:cip-dev-bounces@...] On Behalf Of Ben Hutchings
Sent: Monday, May 29, 2017 11:13 AM
To: cip-dev@...
Subject: [!][cip-dev] Kernel feature support - filesystems and networking

I apologise for the long delay in responding to the kernel config files I was given. Here's a
first list of features I would like to *not* support. I expect to be able to send additional lists
soon. Let me know if you really need some of the features listed below, and if you have
any ideas about how to mitigate the problems I see.

The following features are enabled in some of the configurations I was sent but seem to
be unsupportable over CIP's time scale:

File systems:
- btrfs (CONFIG_BTRFS_FS)
- Too rapidly changing to backport most fixes
- ceph (CONFIG_CEPH_LIB, CONFIG_CEPH_FS)
- Complex network protocol which is likely to need many fixes
- cifs (CONFIG_CIFS_FS)
- Complex network protocol which is likely to need many fixes
- nfs (CONFIG_NFS_FS, CONFIG_NFSD)
- Complex network protocol which is likely to need many fixes
- ufs (CONFIG_UFS_FS)
- No work by current maintainer for 7 years
- xfs (CONFIG_XFS_FS)
- Maintainers unsupportive of backporting fixes

Networking:
- batman-adv (CONFIG_BATMAN_ADV)
- Rapidly changing
- caif (CONFIG_CAIF)
- No work by current maintainer for 5 years
- dcb (CONFIG_DCB)
- No current maintainer
- hsr (CONFIG_HSR)
- No work by current maintainer for 2 years
- llc2 (CONFIG_LLC2)
- No work by current maintainer for 7 years
- phonet (CONFIG_PHONET)
- Dead protocol
- sctp (CONFIG_IP_SCTP)
- Poor security record
- wimax (CONFIG_WIMAX)
- Dead protocol
- x25 (CONFIG_X25)
- Poor security record

I have some doubts about whether these can be supported:

- ntfs (CONFIG_NTFS_FS)
- Fixes are never marked for stable
- overlayfs (CONFIG_OVERLAY_FS)
- I found many apparently important bug fixes in later kernel
versions that have not been backported

Ben.

--
Ben Hutchings
Software Developer, Codethink Ltd.


_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Kernel feature support - filesystems and networking

Ben Hutchings <ben.hutchings@...>
 

I apologise for the long delay in responding to the kernel config files
I was given. Here's a first list of features I would like to *not*
support. I expect to be able to send additional lists soon. Let me
know if you really need some of the features listed below, and if you
have any ideas about how to mitigate the problems I see.

The following features are enabled in some of the configurations I was
sent but seem to be unsupportable over CIP's time scale:

File systems:
- btrfs (CONFIG_BTRFS_FS)
- Too rapidly changing to backport most fixes
- ceph (CONFIG_CEPH_LIB, CONFIG_CEPH_FS)
- Complex network protocol which is likely to need many fixes
- cifs (CONFIG_CIFS_FS)
- Complex network protocol which is likely to need many fixes
- nfs (CONFIG_NFS_FS, CONFIG_NFSD)
- Complex network protocol which is likely to need many fixes
- ufs (CONFIG_UFS_FS)
- No work by current maintainer for 7 years
- xfs (CONFIG_XFS_FS)
- Maintainers unsupportive of backporting fixes

Networking:
- batman-adv (CONFIG_BATMAN_ADV)
- Rapidly changing
- caif (CONFIG_CAIF)
- No work by current maintainer for 5 years
- dcb (CONFIG_DCB)
- No current maintainer
- hsr (CONFIG_HSR)
- No work by current maintainer for 2 years
- llc2 (CONFIG_LLC2)
- No work by current maintainer for 7 years
- phonet (CONFIG_PHONET)
- Dead protocol
- sctp (CONFIG_IP_SCTP)
- Poor security record
- wimax (CONFIG_WIMAX)
- Dead protocol
- x25 (CONFIG_X25)
- Poor security record

I have some doubts about whether these can be supported:

- ntfs (CONFIG_NTFS_FS)
- Fixes are never marked for stable
- overlayfs (CONFIG_OVERLAY_FS)
- I found many apparently important bug fixes in later kernel
versions that have not been backported

Ben.

--
Ben Hutchings
Software Developer, Codethink Ltd.


Linux 4.4.69-cip4

Ben Hutchings <ben.hutchings@...>
 

I've released Linux version 4.4.69-cip4. There are no new CIP-specific
changes; this just adds the fixes from stable versions 4.4.56-4.4.69
inclusive. I reviewed those fixes, but have only done very basic manual
testing of the result.

Ben.

--
Ben Hutchings
Software Developer, Codethink Ltd.


Re: Toolchain Version

Noriaki Fukuyasu <fukuyasu@...>
 

>I’m afraid that I cannot make OSS-J, so won’t be able to drive this conversation next week!

 

Ah, too bad!  




On Wed, May 24, 2017 at 11:04 PM, Chris Paterson <Chris.Paterson2@...> wrote:

Hello Nori-san,

 

I’m afraid that I cannot make OSS-J, so won’t be able to drive this conversation next week!

 

I agree that it would be worth a discussion though.

 

Kind regards, Chris

 

From: Noriaki Fukuyasu [mailto:fukuyasu@linuxfoundation.org]
Sent: 24 May 2017 15:03
To: Chris Paterson <Chris.Paterson2@...>
Cc: Agustin Benito Bethencourt <agustin.benito@....uk>; cip-dev@...
Subject: Re: [cip-dev] Toolchain Version

 

Hi Chris

 

I think is must be a great agenda for our open workshop next week.

May be you can take an ownership of the agenda during the workshop.

 

What do you think?

 

regards

 

Nori

 

 

 

On Wed, May 24, 2017 at 9:34 PM, Chris Paterson <Chris.Paterson2@...> wrote:

Hello,

> From: cip-dev-bounces@...project.org [mailto:cip-dev-
> bounces@...] On Behalf Of Agustin Benito Bethencourt
> Sent: 24 May 2017 11:25
> Hi,
>
> On 24/05/17 09:16, Chris Paterson wrote:
> > Hello all,
> >
> > Has the project decided upon the compiler/toolchain (and version) that
> > will be used?
>
> No.

Should it? I would have thought that as part of CIPs reproducible build/test environment we should be aiming to standardise all tools?

What toolchain is everyone using at the moment?

Kind regards, Chris


>
> >
> > Thanks, Chris
> >
> >
> >
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev@...
> > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
>
> --
> Agustin Benito Bethencourt
> Principal Consultant - FOSS at Codethink agustin.benito@...
> _______________________________________________
> cip-dev mailing list
> cip-dev@...
> https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev



 

--

Noriaki Fukuyasu

 

VP of Japan Operations

The Linux Foundation




--
Noriaki Fukuyasu

VP of Japan Operations
The Linux Foundation
Tel: +81-80-4350-1133


Re: Toolchain Version

Chris Paterson
 

Hello Nori-san,

 

I’m afraid that I cannot make OSS-J, so won’t be able to drive this conversation next week!

 

I agree that it would be worth a discussion though.

 

Kind regards, Chris

 

From: Noriaki Fukuyasu [mailto:fukuyasu@...]
Sent: 24 May 2017 15:03
To: Chris Paterson <Chris.Paterson2@...>
Cc: Agustin Benito Bethencourt <agustin.benito@...>; cip-dev@...
Subject: Re: [cip-dev] Toolchain Version

 

Hi Chris

 

I think is must be a great agenda for our open workshop next week.

May be you can take an ownership of the agenda during the workshop.

 

What do you think?

 

regards

 

Nori

 

 

 

On Wed, May 24, 2017 at 9:34 PM, Chris Paterson <Chris.Paterson2@...> wrote:

Hello,

> From: cip-dev-bounces@... [mailto:cip-dev-
> bounces@...] On Behalf Of Agustin Benito Bethencourt
> Sent: 24 May 2017 11:25
> Hi,
>
> On 24/05/17 09:16, Chris Paterson wrote:
> > Hello all,
> >
> > Has the project decided upon the compiler/toolchain (and version) that
> > will be used?
>
> No.

Should it? I would have thought that as part of CIPs reproducible build/test environment we should be aiming to standardise all tools?

What toolchain is everyone using at the moment?

Kind regards, Chris


>
> >
> > Thanks, Chris
> >
> >
> >
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev@...
> > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
>
> --
> Agustin Benito Bethencourt
> Principal Consultant - FOSS at Codethink agustin.benito@...
> _______________________________________________
> cip-dev mailing list
> cip-dev@...
> https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev



 

--

Noriaki Fukuyasu

 

VP of Japan Operations

The Linux Foundation

Tel: +81-80-4350-1133


Re: Toolchain Version

Noriaki Fukuyasu <fukuyasu@...>
 

Hi Chris

I think is must be a great agenda for our open workshop next week.
May be you can take an ownership of the agenda during the workshop.

What do you think?

regards

Nori



On Wed, May 24, 2017 at 9:34 PM, Chris Paterson <Chris.Paterson2@...> wrote:
Hello,

> From: cip-dev-bounces@...project.org [mailto:cip-dev-
> bounces@...] On Behalf Of Agustin Benito Bethencourt
> Sent: 24 May 2017 11:25
> Hi,
>
> On 24/05/17 09:16, Chris Paterson wrote:
> > Hello all,
> >
> > Has the project decided upon the compiler/toolchain (and version) that
> > will be used?
>
> No.

Should it? I would have thought that as part of CIPs reproducible build/test environment we should be aiming to standardise all tools?

What toolchain is everyone using at the moment?

Kind regards, Chris

>
> >
> > Thanks, Chris
> >
> >
> >
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev@...
> > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
>
> --
> Agustin Benito Bethencourt
> Principal Consultant - FOSS at Codethink agustin.benito@...
> _______________________________________________
> cip-dev mailing list
> cip-dev@...
> https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev



--
Noriaki Fukuyasu

VP of Japan Operations
The Linux Foundation
Tel: +81-80-4350-1133


Re: Toolchain Version

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 24/05/17 13:34, Chris Paterson wrote:
Hello,

From: cip-dev-bounces@... [mailto:cip-dev-
bounces@...] On Behalf Of Agustin Benito Bethencourt
Sent: 24 May 2017 11:25
Hi,

On 24/05/17 09:16, Chris Paterson wrote:
Hello all,

Has the project decided upon the compiler/toolchain (and version) that
will be used?
No.
Should it?
Yes we should.

I would have thought that as part of CIPs reproducible build/test environment we should be aiming to standardise all tools?
We should.


What toolchain is everyone using at the moment?
Good question to start.


Kind regards, Chris



Thanks, Chris



_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink agustin.benito@...
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Re: Toolchain Version

Chris Paterson
 

Hello,

From: cip-dev-bounces@... [mailto:cip-dev-
bounces@...] On Behalf Of Agustin Benito Bethencourt
Sent: 24 May 2017 11:25
Hi,

On 24/05/17 09:16, Chris Paterson wrote:
Hello all,

Has the project decided upon the compiler/toolchain (and version) that
will be used?
No.
Should it? I would have thought that as part of CIPs reproducible build/test environment we should be aiming to standardise all tools?

What toolchain is everyone using at the moment?

Kind regards, Chris



Thanks, Chris



_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink agustin.benito@...
_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Re: Toolchain Version

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 24/05/17 09:16, Chris Paterson wrote:
Hello all,

Has the project decided upon the compiler/toolchain (and version) that
will be used?
No.


Thanks, Chris



_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Toolchain Version

Chris Paterson
 

Hello all,

 

Has the project decided upon the compiler/toolchain (and version) that will be used?

 

 

Thanks, Chris


Re: B @ D 0.9 deployment (was Re: B @ D 0.9 Gold Master)

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 18/05/17 11:55, Robert Marshall wrote:
Robert Marshall <robert.marshall@...> writes:

We are about to close https://gitlab.com/cip-project/testing/issues/85 -
B @ D 0.9 Gold Master declaration and thus we are declaring that the Gold
Master for release 0.9 is ready and we will move onto the deployment
phase (issue 86).

Thank you for your support, encouragement and even (especially?) the bug
reports.
The package and the sources are now deployed and we will close
https://gitlab.com/cip-project/testing/issues/86 - you can find the
links to the downloadable files with that issue - and we will now move
onto the release documentation -
https://gitlab.com/cip-project/testing/issues/37

The release of B@D is scheduled for May 23rd at 11:00 UTC.
The license review process has not finished so we will wait for it before releasing the testing environment. I will let you know when is done and the new release date.


Best Regards

--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Re: CIP open workshop at OSSJ: May 30th from 15:00 to 17:00 hours

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 03/05/17 11:16, Agustin Benito Bethencourt wrote:
Dear CIP friends,

the day before the OSSJ starts, on May 30th, CIP will have a full day of
meetings.

We are organising an open workshop to talk, present, demo and work on
technical topics that might be of interest to this Initiative.

The workshop will take place from 15:00 hours to 17:00 hours on May 30th
in a room (to be determined) at the OSSJ venue.

Please follow up the news about this activity in our wiki page[1]

++ Open workshop. Who can participate?

The workshop is open to all of you who are interested, no matter if you
are CIP Members or not. For those of you who are not yet part of CIP, it
will be a great opportunity to know a little more about who we are and
what we do.

++ How can I register?

If you are attending, it is very important that you tell us in advance
since we need to plan the room capacity accordingly. There are two ways
in which you can confirm your participation:

1.- Through this mailing list, by providing the following information:
* Name.
* Company.
* Position/role.
* Topics you are interested on.

2.- Directly adding your name to the participants table on the wiki[1].

Please check the wiki page anyway for updates. Again, this is an open
workshop. Feel free to join.

++ Can I propose topics?

Yes. Please send your suggestions to this cip-dev mailing list so we
create the agenda as soon as possible.
I would like to propose a discussion about the next steps ion the testing project.

Please read the current plan in the CIP Testing landing page, Action 2: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting#action-2cip-kernel-testing



[1]
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences#workshops-and-meetings


Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Re: Call for translations: social media messages

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 19/05/17 16:23, Agustin Benito Bethencourt wrote:
Hi,

any news have a greater impact if it is communicated in the readers
native language.

I have published some social media messages in the wiki[1] that will be
used to spread the word about the testing tools we are about to release
(May 23rd at 11:00 UTC), hoping that you you could help the CIP testing
team to translate them to other languages.

This way not just the Linux Foundation but any of you can spread the
word in your own language.

Feel free to add a new column for the translation of the messages into
your own language. I added also the release announcement in case you
want to translate it also.
Some of you might not have edit rights for the wiki. I will bring here the process to get them, meanwhile, feel free to translate the messages through the mailing mlist. I will add them to the wiki:

^ RD-1 | Learn about the testing effort within the @linuxfoundation CIP initiative http://bit.ly/2mZMHmx #ciptesting #linux

^ RT-12 | Interested in kernel & embedded linux testing? CIP will have news tomorrow http://bit.ly/2mZMHmx #ciptesting #linux #linuxfoundation

^ RT-1 | What if you could test a kernel in your board connected to your laptop using #lava & #kernelci ? #ciptesting #linux #linuxfoundation

^ RT | CIP project released VM with #lava & #kernelci to test #linux kernels locally More news http://bit.ly/2q48uae #linuxfoundation #ciptesting |

^ RT+1 | #linux kernel testing with #lava & #kernelci in a VM. Check the news from CIP project http://bit.ly/2q48uae #ciptesting #linuxfoundation

^ RT+12 | Interested in #lava & #kernelci ? Now integrated in a VM you can deploy & use http://bit.ly/2q48uae #ciptesting #linux #linuxfoundation

^ RD+1 | Learn more about the #ciptesting effort to test the CIP #linux kernel at the #OSSummit in booth http://bit.ly/2q48uae #linuxfoundation

Link: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingmanagement#marketing-material-and-plan


^ RD-1 | The Civil Infrastructure Platform is a Linux Foundation initiative focused on building a commodity industrial grade Linux based system and maintain it over a long period of time. Testing this system is an strategic activity. Tomorrow May 23rd the CIP testing team will release their first deliverable, a Virtual Machine where LAVA and KernelCI have been integrated in order for any developer to test linux kernels, like the CIP kernel, in her own machine with a reference board attached to it. Learn more about this testing effort and stay tuned for the release announcement. https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting.

^ RT | The Civil Infrastructure Platform, a Linux Foundation Initiative is happy to announce the release of a Debian based Virtual Machine that will allow developers to test Linux kernels on a board attached to their own machine using LAVA and KernelCI, that is, the same tools used in the successful kernelci.org project. Check the release announcement for further information: http://bit.ly/2q48uae

^ RD+1 | If you are interested in testing Linux kernels please take a look at what the CIP testing project is doing. LAVA and KernelCI have been integrated in a single Debian based virtual machine allowing any developer to use these tools to test a kernel in a board attached to their own computer. The CIP developers have also created a step by step howto that severely simplifies the configuration process. Try it out and let them know what you think. http://bit.ly/2q48uae


Thank you very much in advance for your collaboration.

[1]
https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingmanagement#marketing-material-and-plan


Best regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Call for translations: social media messages

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

any news have a greater impact if it is communicated in the readers native language.

I have published some social media messages in the wiki[1] that will be used to spread the word about the testing tools we are about to release (May 23rd at 11:00 UTC), hoping that you you could help the CIP testing team to translate them to other languages.

This way not just the Linux Foundation but any of you can spread the word in your own language.

Feel free to add a new column for the translation of the messages into your own language. I added also the release announcement in case you want to translate it also.

Thank you very much in advance for your collaboration.

[1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingmanagement#marketing-material-and-plan

Best regards

--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


Re: B @ D 0.9 deployment (was Re: B @ D 0.9 Gold Master)

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 18/05/17 11:55, Robert Marshall wrote:
Robert Marshall <robert.marshall@...> writes:

We are about to close https://gitlab.com/cip-project/testing/issues/85 -
B @ D 0.9 Gold Master declaration and thus we are declaring that the Gold
Master for release 0.9 is ready and we will move onto the deployment
phase (issue 86).

Thank you for your support, encouragement and even (especially?) the bug
reports.
The package and the sources are now deployed and we will close
https://gitlab.com/cip-project/testing/issues/86 - you can find the
links to the downloadable files with that issue - and we will now move
onto the release documentation -
https://gitlab.com/cip-project/testing/issues/37

The release of B@D is scheduled for May 23rd at 11:00 UTC.
Please do not spread the links on #86 before the release. The will be structured and described in the Download page and promoted on the Release Day.


Robert


_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...


B @ D 0.9 deployment (was Re: B @ D 0.9 Gold Master)

Robert Marshall <robert.marshall@...>
 

Robert Marshall <robert.marshall@...> writes:

We are about to close https://gitlab.com/cip-project/testing/issues/85 -
B @ D 0.9 Gold Master declaration and thus we are declaring that the Gold
Master for release 0.9 is ready and we will move onto the deployment
phase (issue 86).

Thank you for your support, encouragement and even (especially?) the bug
reports.
The package and the sources are now deployed and we will close
https://gitlab.com/cip-project/testing/issues/86 - you can find the
links to the downloadable files with that issue - and we will now move
onto the release documentation -
https://gitlab.com/cip-project/testing/issues/37

The release of B@D is scheduled for May 23rd at 11:00 UTC.

Robert


Re: CIP TSC meeting minutes (15 May 2017)

Annie Fisher <afisher@...>
 

Thank you!

Annie Fisher, MPA CSM
Program Manager, The Linux Foundation
Location & Time-zone: San Francisco, CA, PST
email: afisher@...


On Tue, May 16, 2017 at 2:00 AM, KOBAYASHI Yoshitake <yoshitake.kobayashi@...> wrote:
Hi all,

I uploaded meeting minutes for CIP TSC conference call on 15th May.
https://wiki.linuxfoundation.org/civilinfrastructureplatform/tsc-meetings/tsc_mm_may152017

Best regards,
Yoshi


_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Re: B @ D 0.9 Gold Master

Agustin Benito Bethencourt <agustin.benito@...>
 

Hi,

On 16/05/17 15:01, Robert Marshall wrote:
We are about to close https://gitlab.com/cip-project/testing/issues/85 -
B @ D 0.9 Gold Master declaration and thus we are declaring that the Gold
Master for release 0.9 is ready and we will move onto the deployment
phase (issue 86).

Thank you for your support, encouragement and even (especially?) the bug
reports.
So the release of B@D is scheduled for May 23rd at 11:00 UTC Now we will concentrate in the following tasks:
* Deployment: #86 https://gitlab.com/cip-project/testing/issues/86
* Other release related tasks you can follow from #37 https://gitlab.com/cip-project/testing/issues/37

Best Regards

--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...

8361 - 8380 of 8627