From sara at sinodun.com  Wed Nov  6 16:34:22 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 6 Nov 2013 16:34:22 +0000
Subject: [Opendnssec-develop] RE: Team meeting - Thursday 7 Nov @ 14:00 CET
Message-ID: <60E197D2-A5E5-4EDC-B2CA-0CB0D3FC149C@sinodun.com>

Hi All, 

We have a team meeting on Thursday this week (tomorrow) :

Date:      Thursday 7 Nov 2013
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
Method:  Teamspeak
Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-07+Agenda


Sara.



From sara at sinodun.com  Thu Nov  7 15:33:02 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 7 Nov 2013 15:33:02 +0000
Subject: Fwd: [Opendnssec-develop] RE: Team meeting - Thursday 7 Nov @ 14:00
	CET
References: <60E197D2-A5E5-4EDC-B2CA-0CB0D3FC149C@sinodun.com>
Message-ID: <4CA73726-061E-41C5-AAC0-3188CA67A859@sinodun.com>

Hi All, 

The minutes from the meeting today are available for review:

https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-07+Minutes

The next meeting is planned for:

Date:      Thursday 21 Nov 2013
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC

Sara. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenDNSSEC meeting.ics
Type: text/calendar
Size: 713 bytes
Desc: not available
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131107/1dee0557/attachment.bin>
-------------- next part --------------



Begin forwarded message:

> From: Sara Dickinson <sara at sinodun.com>
> Date: 6 November 2013 16:34:22 GMT
> To: "opendnssec-develop at lists.opendnssec.org Developers" <Opendnssec-develop at lists.opendnssec.org>
> Subject: [Opendnssec-develop] RE: Team meeting - Thursday 7 Nov @ 14:00 CET
> 
> Hi All, 
> 
> We have a team meeting on Thursday this week (tomorrow) :
> 
> Date:      Thursday 7 Nov 2013
> Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
> Method:  Teamspeak
> Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-07+Agenda
> 
> 
> Sara.
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop


From sara at sinodun.com  Thu Nov  7 15:33:51 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 7 Nov 2013 15:33:51 +0000
Subject: [Opendnssec-develop] RE: Code review process
Message-ID: <83576388-EB46-4C17-99F8-73A81EFC92F9@sinodun.com>

Hi All, 

I meant to mention when Jakob was talking about the move to github today that Warren and I have been working using a pre-commit review process in Crucible. It is now documented here:
https://wiki.opendnssec.org/display/OpenDNSSEC/Code+Review+process
Basically a patch can be uploaded that Crucible automatically turns into a nice graphical diff for comments (just like reviewing a svn commit). 

Also I have made some clarifications and minor tweaks to the Issue tracking process based on feedback from Warren:
https://wiki.opendnssec.org/display/OpenDNSSEC/Issue+tracking+process

Comments/feedback welcomed and thanks to Warren for all his patience in this!

Sara. 





From jerry at opendnssec.org  Fri Nov  8 12:59:02 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 8 Nov 2013 13:59:02 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>
	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
Message-ID: <CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>

Hi,

On Mon, Oct 28, 2013 at 5:29 PM, Sara Dickinson <sara at sinodun.com> wrote:

> Please find a wiki page with details of the developer workshop and a first
> pass at a draft agenda here:
>
>
> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013
>
> Please let me know if you have any topics you would like covered at the
> workshop that are not on this agenda, have any suggestions for other
> sessions we could have or if you would like any sessions moved around.
>

I would like to add a few topic at/around Moving to Git + more:

- What is Git?
Short intro into Git. I can talk some what it is and whats different from
SVN but this would be more giving if everyone can come up with
questions/fears about Git before hand and I can try and answer them.

- A workflow proposal: How we can work with Github
This workflow is based on the workflow created at .SE where the development
department has done the exact same thing we are doing. At .SE we used SVN
in the same manner, one repository for many softwares, moved it to
Atlassian Stash (a Github clone since we can't put it outside our
infrastructure) to one repository for each software and developed a
proccess with integrated review for quality control.

- Git Flow: What is it? How I use it. How you can use it.
Git Flow is a way of working in Git that comes with Git integrated tools
that helps you a lot, instead of having know 10-15 git commands you have
about 4. I can talk shortly on what the ideas behind the process is, how I
use it for other softwares and how we can use it in OpenDNSSEC with regards
to the workflow proposal.

=====

If people wants to have a workshop with Git we might need to rearrange the
agenda some, maybe move 2.0 to the morning after and have a half day Git
the later part of the first day.

=====

- Jenkins and testing platform
The testing platforms are due for an upgrade. I can give a short
presentation on how it works today and whats going to change. We can also
talk about OS/arch support.

I also want to warn everyone right now that the talks might not be well
prepared since I will have one day, before the meet, to prepare them! So
there will probably be a lot of Uhm's.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131108/526d7804/attachment.htm>

From sara at sinodun.com  Fri Nov  8 13:46:03 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 8 Nov 2013 13:46:03 +0000
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>
	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
Message-ID: <4FF30807-E107-4890-9D72-A14083CEE802@sinodun.com>

Hi Jerry, 

Jakob brought this up in the team meeting yesterday (I had the impression that he would be doing the presentation though... no difference). I'll shuffle the agenda to try to accommodate this. 

Jerry - just to be clear - you plan to be around for all 3 days of the workshop now? Maybe it would be better to do the git & testing stuff on Friday morning to give you/Jakob as much time as possible to prepare?

Sara.  

On 8 Nov 2013, at 12:59, Jerry Lundstr?m wrote:

> Hi,
> 
> On Mon, Oct 28, 2013 at 5:29 PM, Sara Dickinson <sara at sinodun.com> wrote:
> Please find a wiki page with details of the developer workshop and a first pass at a draft agenda here:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013
> 
> Please let me know if you have any topics you would like covered at the workshop that are not on this agenda, have any suggestions for other sessions we could have or if you would like any sessions moved around.
> 
> I would like to add a few topic at/around Moving to Git + more:
> 
> - What is Git?
> Short intro into Git. I can talk some what it is and whats different from SVN but this would be more giving if everyone can come up with questions/fears about Git before hand and I can try and answer them.
> 
> - A workflow proposal: How we can work with Github
> This workflow is based on the workflow created at .SE where the development department has done the exact same thing we are doing. At .SE we used SVN in the same manner, one repository for many softwares, moved it to Atlassian Stash (a Github clone since we can't put it outside our infrastructure) to one repository for each software and developed a proccess with integrated review for quality control.
> 
> - Git Flow: What is it? How I use it. How you can use it.
> Git Flow is a way of working in Git that comes with Git integrated tools that helps you a lot, instead of having know 10-15 git commands you have about 4. I can talk shortly on what the ideas behind the process is, how I use it for other softwares and how we can use it in OpenDNSSEC with regards to the workflow proposal.
> 
> =====
> 
> If people wants to have a workshop with Git we might need to rearrange the agenda some, maybe move 2.0 to the morning after and have a half day Git the later part of the first day.
> 
> =====
> 
> - Jenkins and testing platform
> The testing platforms are due for an upgrade. I can give a short presentation on how it works today and whats going to change. We can also talk about OS/arch support.
> 
> I also want to warn everyone right now that the talks might not be well prepared since I will have one day, before the meet, to prepare them! So there will probably be a lot of Uhm's.
> 
> -- 
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/



From jerry at opendnssec.org  Fri Nov  8 14:42:26 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 8 Nov 2013 15:42:26 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <4FF30807-E107-4890-9D72-A14083CEE802@sinodun.com>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>
	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
	<4FF30807-E107-4890-9D72-A14083CEE802@sinodun.com>
Message-ID: <CAGTFMNbxfLEgD71OsFFmxtL+QDMzRnnANsncVOv-D_OxNWbOiA@mail.gmail.com>

On Fri, Nov 8, 2013 at 2:46 PM, Sara Dickinson <sara at sinodun.com> wrote:

> Jerry - just to be clear - you plan to be around for all 3 days of the
> workshop now? Maybe it would be better to do the git & testing stuff on
> Friday morning to give you/Jakob as much time as possible to prepare?
>

I might need to leave early before the xmas party since there will be a
preparty at the office and there are a lot of stuff that needs setting up.
But I will know more when I get back on the 10th.

I would personally prefer to do it on before the party since it might be a
"slow" morning after :) Also there isn't that much time to prepare during
our meet, better to attend it 100%.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131108/9ae5e466/attachment.htm>

From sara at sinodun.com  Thu Nov 14 11:42:44 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 14 Nov 2013 11:42:44 +0000
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>
	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
Message-ID: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>

Hi All, 

I have slightly updated the agenda for the developers workshop:
https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013

Jakob - since Jerry clearly has other prior commitments would you be able to put some material together on the move to git? We could do a short git workshop first thing Thursday if people think they need it. 

Thanks

Sara.


On 8 Nov 2013, at 12:59, Jerry Lundstr?m wrote:

> Hi,
> 
> On Mon, Oct 28, 2013 at 5:29 PM, Sara Dickinson <sara at sinodun.com> wrote:
> Please find a wiki page with details of the developer workshop and a first pass at a draft agenda here:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013
> 
> Please let me know if you have any topics you would like covered at the workshop that are not on this agenda, have any suggestions for other sessions we could have or if you would like any sessions moved around.
> 
> I would like to add a few topic at/around Moving to Git + more:
> 
> - What is Git?
> Short intro into Git. I can talk some what it is and whats different from SVN but this would be more giving if everyone can come up with questions/fears about Git before hand and I can try and answer them.
> 
> - A workflow proposal: How we can work with Github
> This workflow is based on the workflow created at .SE where the development department has done the exact same thing we are doing. At .SE we used SVN in the same manner, one repository for many softwares, moved it to Atlassian Stash (a Github clone since we can't put it outside our infrastructure) to one repository for each software and developed a proccess with integrated review for quality control.
> 
> - Git Flow: What is it? How I use it. How you can use it.
> Git Flow is a way of working in Git that comes with Git integrated tools that helps you a lot, instead of having know 10-15 git commands you have about 4. I can talk shortly on what the ideas behind the process is, how I use it for other softwares and how we can use it in OpenDNSSEC with regards to the workflow proposal.
> 
> =====
> 
> If people wants to have a workshop with Git we might need to rearrange the agenda some, maybe move 2.0 to the morning after and have a half day Git the later part of the first day.
> 
> =====
> 
> - Jenkins and testing platform
> The testing platforms are due for an upgrade. I can give a short presentation on how it works today and whats going to change. We can also talk about OS/arch support.
> 
> I also want to warn everyone right now that the talks might not be well prepared since I will have one day, before the meet, to prepare them! So there will probably be a lot of Uhm's.
> 
> -- 
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/



From matthijs at nlnetlabs.nl  Thu Nov 14 14:32:54 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Thu, 14 Nov 2013 15:32:54 +0100
Subject: [Opendnssec-develop] A successful Git branching model
Message-ID: <5284DF16.8040001@nlnetlabs.nl>

This is the git model we are considering to use for NLnet Labs (Willem
already uses it for getdns-api)

  http://nvie.com/posts/a-successful-git-branching-model/

It also explains Git shortly but nicely in a conceptual way.

Best regards,
  Matthijs


From matthijs at nlnetlabs.nl  Thu Nov 14 14:34:47 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Thu, 14 Nov 2013 15:34:47 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
Message-ID: <5284DF87.7090808@nlnetlabs.nl>

Hi Jerry,

On 11/08/2013 01:59 PM, Jerry Lundstr?m wrote:
> Hi,
> 
> On Mon, Oct 28, 2013 at 5:29 PM, Sara Dickinson <sara at sinodun.com
> <mailto:sara at sinodun.com>> wrote:
> 
>     Please find a wiki page with details of the developer workshop and a
>     first pass at a draft agenda here:
> 
>     https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013
> 
>     Please let me know if you have any topics you would like covered at
>     the workshop that are not on this agenda, have any suggestions for
>     other sessions we could have or if you would like any sessions moved
>     around.
> 
> 
> I would like to add a few topic at/around Moving to Git + more:
> 
> - What is Git?
> Short intro into Git. I can talk some what it is and whats different
> from SVN but this would be more giving if everyone can come up with
> questions/fears about Git before hand and I can try and answer them.

In the teleconf Jakob suggested that all developers get familiar with
git before the developer meeting. I think that is a good idea. If
everybody does that, there is no need to do an introduction on Git
during the workshop.


> - A workflow proposal: How we can work with Github
> This workflow is based on the workflow created at .SE where the
> development department has done the exact same thing we are doing. At
> .SE we used SVN in the same manner, one repository for many softwares,
> moved it to Atlassian Stash (a Github clone since we can't put it
> outside our infrastructure) to one repository for each software and
> developed a proccess with integrated review for quality control.

Can you share .SE's workflow on this list? Again, I think it would be
good if we can get familiar with the proposals before the meeting starts.

Thanks.

Best regards,
  Matthijs

> - Git Flow: What is it? How I use it. How you can use it.
> Git Flow is a way of working in Git that comes with Git integrated tools
> that helps you a lot, instead of having know 10-15 git commands you have
> about 4. I can talk shortly on what the ideas behind the process is, how
> I use it for other softwares and how we can use it in OpenDNSSEC with
> regards to the workflow proposal.
> 
> =====
> 
> If people wants to have a workshop with Git we might need to rearrange
> the agenda some, maybe move 2.0 to the morning after and have a half day
> Git the later part of the first day.
> 
> =====
> 
> - Jenkins and testing platform
> The testing platforms are due for an upgrade. I can give a short
> presentation on how it works today and whats going to change. We can
> also talk about OS/arch support.
> 
> I also want to warn everyone right now that the talks might not be well
> prepared since I will have one day, before the meet, to prepare them! So
> there will probably be a lot of Uhm's.
> 
> -- 
> Jerry Lundstr?m - OpenDNSSEC Developer
> http://www.opendnssec.org/
> 
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 



From sara at sinodun.com  Thu Nov 14 15:24:09 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 14 Nov 2013 15:24:09 +0000
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <5284DF16.8040001@nlnetlabs.nl>
References: <5284DF16.8040001@nlnetlabs.nl>
Message-ID: <05EC92DE-1777-475B-8D9B-52A3ACAFF60A@sinodun.com>

Hi Matthijs, 

Many thanks for this - very good article. I guess http://git-scm.com/doc is also a useful reference point. 

Jakob - in the teleconference we also talked about you sending out an email with some git resources in it to help developers prepare? 

Unfortunately Jerry is on vacation until the day before the workshop so I don't know if anyone else can share the .SE workflow....?

Sara.

On 14 Nov 2013, at 14:32, Matthijs Mekking wrote:

> This is the git model we are considering to use for NLnet Labs (Willem
> already uses it for getdns-api)
> 
>  http://nvie.com/posts/a-successful-git-branching-model/
> 
> It also explains Git shortly but nicely in a conceptual way.
> 
> Best regards,
>  Matthijs
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop



From jad at sinodun.com  Thu Nov 14 15:34:32 2013
From: jad at sinodun.com (John Dickinson)
Date: Thu, 14 Nov 2013 15:34:32 +0000
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <5284DF16.8040001@nlnetlabs.nl>
References: <5284DF16.8040001@nlnetlabs.nl>
Message-ID: <9026B139-6B88-4E60-8F5C-91C97E5AFFDD@sinodun.com>

man gittutorial
man gittutorial-2

John

On 14 Nov 2013, at 14:32, Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:

> This is the git model we are considering to use for NLnet Labs (Willem
> already uses it for getdns-api)
> 
>  http://nvie.com/posts/a-successful-git-branching-model/
> 
> It also explains Git shortly but nicely in a conceptual way.
> 
> Best regards,
>  Matthijs
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131114/0ed54c75/attachment.bin>

From jad at sinodun.com  Thu Nov 14 16:21:49 2013
From: jad at sinodun.com (John Dickinson)
Date: Thu, 14 Nov 2013 16:21:49 +0000
Subject: [Opendnssec-develop] A successful Git branching model
In-Reply-To: <9026B139-6B88-4E60-8F5C-91C97E5AFFDD@sinodun.com>
References: <5284DF16.8040001@nlnetlabs.nl>
	<9026B139-6B88-4E60-8F5C-91C97E5AFFDD@sinodun.com>
Message-ID: <DD84FE11-6DEC-4EDA-A56B-793061439004@sinodun.com>

Oh - and this

man gitworkflows

John

On 14 Nov 2013, at 15:34, John Dickinson <jad at sinodun.com> wrote:

> man gittutorial
> man gittutorial-2
> 
> John
> 
> On 14 Nov 2013, at 14:32, Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:
> 
>> This is the git model we are considering to use for NLnet Labs (Willem
>> already uses it for getdns-api)
>> 
>> http://nvie.com/posts/a-successful-git-branching-model/
>> 
>> It also explains Git shortly but nicely in a conceptual way.
>> 
>> Best regards,
>> Matthijs
>> _______________________________________________
>> Opendnssec-develop mailing list
>> Opendnssec-develop at lists.opendnssec.org
>> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131114/42c80e60/attachment.bin>

From jerry at opendnssec.org  Fri Nov 15 16:05:40 2013
From: jerry at opendnssec.org (=?ISO-8859-1?Q?Jerry_Lundstr=F6m?=)
Date: Fri, 15 Nov 2013 12:05:40 -0400
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <19232154.56323.1384465072931.JavaMail.mobile-sync@vcyf7>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>
	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
	<19232154.56323.1384465072931.JavaMail.mobile-sync@vcyf7>
Message-ID: <-4679553162002352190@unknownmsgid>

On holiday until dev meet.

-- 
Jerry Lundstr?m - OpenDNSSEC Developer
http://www.opendnssec.org/

On 14 nov 2013, at 10:34, Matthijs Mekking <matthijs at nlnetlabs.nl> wrote:

Hi Jerry,

On 11/08/2013 01:59 PM, Jerry Lundstr?m wrote:

Hi,


On Mon, Oct 28, 2013 at 5:29 PM, Sara Dickinson <sara at sinodun.com

<mailto:sara at sinodun.com <sara at sinodun.com>>> wrote:


   Please find a wiki page with details of the developer workshop and a

   first pass at a draft agenda here:



https://wiki.opendnssec.org/display/OpenDNSSEC/Developer+Workshop+-+Stockholm+Dec+2013


   Please let me know if you have any topics you would like covered at

   the workshop that are not on this agenda, have any suggestions for

   other sessions we could have or if you would like any sessions moved

   around.



I would like to add a few topic at/around Moving to Git + more:


- What is Git?

Short intro into Git. I can talk some what it is and whats different

from SVN but this would be more giving if everyone can come up with

questions/fears about Git before hand and I can try and answer them.


In the teleconf Jakob suggested that all developers get familiar with
git before the developer meeting. I think that is a good idea. If
everybody does that, there is no need to do an introduction on Git
during the workshop.


- A workflow proposal: How we can work with Github

This workflow is based on the workflow created at .SE where the

development department has done the exact same thing we are doing. At

.SE we used SVN in the same manner, one repository for many softwares,

moved it to Atlassian Stash (a Github clone since we can't put it

outside our infrastructure) to one repository for each software and

developed a proccess with integrated review for quality control.


Can you share .SE's workflow on this list? Again, I think it would be
good if we can get familiar with the proposals before the meeting starts.

Thanks.

Best regards,
 Matthijs

- Git Flow: What is it? How I use it. How you can use it.

Git Flow is a way of working in Git that comes with Git integrated tools

that helps you a lot, instead of having know 10-15 git commands you have

about 4. I can talk shortly on what the ideas behind the process is, how

I use it for other softwares and how we can use it in OpenDNSSEC with

regards to the workflow proposal.


====>

If people wants to have a workshop with Git we might need to rearrange

the agenda some, maybe move 2.0 to the morning after and have a half day

Git the later part of the first day.


====>

- Jenkins and testing platform

The testing platforms are due for an upgrade. I can give a short

presentation on how it works today and whats going to change. We can

also talk about OS/arch support.


I also want to warn everyone right now that the talks might not be well

prepared since I will have one day, before the meet, to prepare them! So

there will probably be a lot of Uhm's.


--

Jerry Lundstr?m - OpenDNSSEC Developer

http://www.opendnssec.org/



_______________________________________________

Opendnssec-develop mailing list

Opendnssec-develop at lists.opendnssec.org

https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop



_______________________________________________
Opendnssec-develop mailing list
Opendnssec-develop at lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131115/f877e113/attachment.htm>

From sara at sinodun.com  Tue Nov 19 12:51:07 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Tue, 19 Nov 2013 12:51:07 +0000
Subject: [Opendnssec-develop] Fwd: OpenDNSSEC Test Co-ordinator
References: <E32064FE-171A-4C44-920A-9EC6D12CBCB4@opendnssec.org>
Message-ID: <693F85E6-DCF0-4A4E-9A76-E13FB30CB887@sinodun.com>

Hi All, 

At the board meeting at the start of the month there was again discussion of the fact that we don't have a dedicated tester in the OpenDNSSEC team and that if we did this would greatly help with the production releases and 2.0 development. I took an action to draw up a first pass outline of what such a role might involve - please see below. I think this would need someone who was available at least a couple days a week to be effective. Comments and feedback on this would be greatly appreciated. 

Once agreed, the next step would be to circulate this description to contributing organisations and also possibly the users list to see if anyone was willing to adopt this role, or contribute resources (people or money) to making it happen. If anyone has thoughts or ideas about this aspect, that would also be helpful!

Best regards

Sara. 

P.S. I'll give a brief update on the board meeting at the next developer team meeting - completely forgot this last meeting!



OpenDNSSEC Test Co-ordinator
-----------------------------------------------

Responsibilities for this role would include:

- Monitoring of regression testing system status
   - Initial investigation of test failures to determine the cause 
   - Depending on the problem either directly implementing a fix or co-ordinating with the relevant developer to solve the problem


- Maintaining and extending the existing test framework
   - Add/update functions in the framework to 
        - improve usability 
        - reduce code duplication
        - make porting tests between branches as simple as possible


- Track and improve existing functional test coverage
   - Working with developers to create tests for new features as they are implemented
   - Improve the tools that analyze the existing test coverage
   - Identify areas missing from the current functional tests
   - Work with developers to increase the coverage


- Performance and Endurance testing
   - Work with the developers to benchmark the performance of the production and development releases
   - Develop endurance and stress tests to model user environments


- System administration of the testing platforms including management of
   -  jenkins test jobs and configuration
   - 15 virtual test machines (jenkins slaves)
   - 1 Dell PowerEdge R310 (performance testing machine)





From jakob at kirei.se  Wed Nov 20 07:05:21 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Wed, 20 Nov 2013 08:05:21 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <5284DF87.7090808@nlnetlabs.nl>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
	<5284DF87.7090808@nlnetlabs.nl>
Message-ID: <3EF456B1-7756-4392-B755-CE25907FC8EC@kirei.se>

On 14 nov 2013, at 15:34, Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:

> In the teleconf Jakob suggested that all developers get familiar with
> git before the developer meeting. I think that is a good idea. If
> everybody does that, there is no need to do an introduction on Git
> during the workshop.

Agreed, we can talk about specifics when we discuss the workflow.

	jakob

-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From jakob at kirei.se  Wed Nov 20 07:33:06 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Wed, 20 Nov 2013 08:33:06 +0100
Subject: [Opendnssec-develop] Developer workshop
In-Reply-To: <4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
References: <995A7115-7B09-4A8C-BD68-646A7C8D31FC@sinodun.com>
	<EA996F7C-613B-4ACF-94BD-FFFAAF970CDB@sinodun.com>
	<CAGTFMNZZUeGSJeDdaD9wRAUpNZ1PfDSCqFnLQL06J4f8d4GBLg@mail.gmail.com>
	<4507936A-DEBA-4D9A-A643-9306CA02C514@sinodun.com>
Message-ID: <C7DAD186-DFC0-4F67-A8F1-5B9C8E9CB5FE@kirei.se>

On 14 nov 2013, at 12:42, Sara Dickinson <sara at sinodun.com> wrote:

> Jakob - since Jerry clearly has other prior commitments would you be able to put some material together on the move to git? We could do a short git workshop first thing Thursday if people think they need it. 

I've gathered the previously sent out links at https://wiki.opendnssec.org/display/OpenDNSSEC/Git. If everyone read this before the workshop we could save a lot of time.

Also make sure you play with git yourself, including looking at https://github.com/opendnssec and http://git.nlnetlabs.nl/ldns/.


	jakob


-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From sara at sinodun.com  Wed Nov 20 13:15:40 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 20 Nov 2013 13:15:40 +0000
Subject: [Opendnssec-develop] Team meeting - Thursday 21 Nov @ 14:00 CET
Message-ID: <EE93DF4E-9C33-4177-82AF-812FF5D1D6A6@sinodun.com>

Hi All, 

We have a team meeting on Thursday this week (tomorrow) :

Date:      Thursday 21 Nov 2013
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
Method:  Teamspeak
Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-21+Agenda

Sara.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131120/b5110af0/attachment.htm>

From sara at sinodun.com  Thu Nov 21 14:33:58 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 21 Nov 2013 14:33:58 +0000
Subject: Fwd: [Opendnssec-develop] Team meeting - Thursday 21 Nov @ 14:00 CET
References: <EE93DF4E-9C33-4177-82AF-812FF5D1D6A6@sinodun.com>
Message-ID: <92501CBC-BD82-45C7-9345-CCDBCE279B96@sinodun.com>

Hi All, 

The minutes from the meeting today are available for review:

https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-21+Minutes

The next meeting is planned for:

Date:      Monday 2 Dec 2013
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC

Sara. 




Begin forwarded message:

> From: Sara Dickinson <sara at sinodun.com>
> Date: 20 November 2013 13:15:40 GMT
> To: Opd Dev <opendnssec-develop at lists.opendnssec.org>
> Subject: [Opendnssec-develop] Team meeting - Thursday 21 Nov @ 14:00 CET
> 
> Hi All, 
> 
> We have a team meeting on Thursday this week (tomorrow) :
> 
> Date:      Thursday 21 Nov 2013
> Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
> Method:  Teamspeak
> Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-21+Agenda
> 
> Sara.
> 
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131121/07916692/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenDNSSEC team meeting.ics
Type: text/calendar
Size: 718 bytes
Desc: not available
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131121/07916692/attachment.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131121/07916692/attachment-0001.htm>

From sara at sinodun.com  Mon Nov 25 09:09:25 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Mon, 25 Nov 2013 09:09:25 +0000
Subject: [Opendnssec-develop] RE: 1.3.16 and 1.4.3 production releases
Message-ID: <AF5C8AEF-2A21-4243-B903-1557DA78B810@sinodun.com>

Hi All, 

As discussed in the team meeting last week the outstanding JIRA issues (330/436 - NSEC3PARAM TTL) have now been completed and so both the 1.3 and 1.4 branches are ready for the next patch releases. Please refrain from submitting any more code into either the 1.3 or 1.4 branch until after the releases unless you are sure it is safe to include in the production release. 

Jakob - since Jerry is on vacation could you please indicate if/when you could possibly create the release candidates for both these releases?

Thanks

Sara. 

From sara at sinodun.com  Mon Nov 25 09:09:25 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Mon, 25 Nov 2013 09:09:25 +0000
Subject: [Opendnssec-develop] RE: 1.3.16 and 1.4.3 production releases
Message-ID: <11F934EB-DC8F-4E84-857A-624F42579F8B@sinodun.com>

Hi All, 

As discussed in the team meeting last week the outstanding JIRA issues (330/436 - NSEC3PARAM TTL) have now been completed and so both the 1.3 and 1.4 branches are ready for the next patch releases. Please refrain from submitting any more code into either the 1.3 or 1.4 branch until after the releases unless you are sure it is safe to include in the production release. 

Jakob - since Jerry is on vacation could you please indicate if/when you could possibly create the release candidates for both these releases?

Thanks

Sara. 

From jad at sinodun.com  Mon Nov 25 15:20:39 2013
From: jad at sinodun.com (John Dickinson)
Date: Mon, 25 Nov 2013 15:20:39 +0000
Subject: [Opendnssec-develop] static analyzer
In-Reply-To: <92501CBC-BD82-45C7-9345-CCDBCE279B96@sinodun.com>
References: <EE93DF4E-9C33-4177-82AF-812FF5D1D6A6@sinodun.com>
	<92501CBC-BD82-45C7-9345-CCDBCE279B96@sinodun.com>
Message-ID: <34E1D1F9-C0E7-4F6A-BC19-FAFD4289E9E5@sinodun.com>


On 21 Nov 2013, at 14:33, Sara Dickinson <sara at sinodun.com> wrote:

> Hi All, 
> 
> The minutes from the meeting today are available for review:
> 
> https://wiki.opendnssec.org/display/OpenDNSSEC/2013-11-21+Minutes


Hi All,

I have been playing with the clang static analyzer. (http://clang-analyzer.llvm.org/)

Results from running it on SoftHSM and OpenDNSSEC can be found at:

https://dev.sinodun.com/analysis/opendnssec/
https://dev.sinodun.com/analysis/softhsm/

AFAIK - the analyser steps through all code paths and flags up those that result in a issue. Some of these are (of course) false positives.

FYI - I ran it like this (On ubuntu 13.10)

export PATH=$PATH:/opt/llvm/bin/:~/Development/clang/llvm/tools/clang/tools/scan-build:~/Development/clang/llvm/tools/clang/tools/scan-view
svn co  http://svn.opendnssec.org/trunk/softHSM SoftHSM
cd SoftHSM
sh autogen.sh
scan-build --use-analyzer /opt/llvm/bin/clang ./configure --with-botan=/usr
scan-build --use-analyzer /opt/llvm/bin/clang make

svn co http://svn.opendnssec.org/trunk/OpenDNSSEC OpenDNSSEC
cd OpenDNSSEC
sh autogen.sh
scan-build --use-analyzer /opt/llvm/bin/clang ./configure
scan-build --use-analyzer /opt/llvm/bin/clang make

regards
John

---
jad at sinodun.com

http://sinodun.com

Sinodun Internet Technologies Ltd.
Stables 4, Suite 11,
Howbery Park,
Wallingford,
Oxfordshire,
OX10 8BA,
U.K.

+44 (0)1491 834957

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131125/411b759b/attachment.bin>

From jad at sinodun.com  Mon Nov 25 17:10:47 2013
From: jad at sinodun.com (John Dickinson)
Date: Mon, 25 Nov 2013 17:10:47 +0000
Subject: [Opendnssec-develop] SUPPORT-86
Message-ID: <F97D9752-8EA4-4069-9336-70DD6C9DA8F1@sinodun.com>

Hi,

I have a few spare cycles so I thought I would try and help.

I can reproduce SUPPORT-86 - build on OS X only works with -D_POSIX_C_SOURCE in CFLAGS.

The build also works with -D_DARWIN_C_SOURCE. From looking at the man page for compat(5) this seems reasonable. Does anyone have any thoughts on which is better.

regards
John


---
jad at sinodun.com

http://sinodun.com

Sinodun Internet Technologies Ltd.
Stables 4, Suite 11,
Howbery Park,
Wallingford,
Oxfordshire,
OX10 8BA,
U.K.

+44 (0)1491 834957

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20131125/3c9c3674/attachment.bin>

From jakob at kirei.se  Tue Nov 26 08:27:59 2013
From: jakob at kirei.se (Jakob Schlyter)
Date: Tue, 26 Nov 2013 09:27:59 +0100
Subject: [Opendnssec-develop] 1.3.16 and 1.4.3 production releases
In-Reply-To: <AF5C8AEF-2A21-4243-B903-1557DA78B810@sinodun.com>
References: <AF5C8AEF-2A21-4243-B903-1557DA78B810@sinodun.com>
Message-ID: <03BF1F10-C951-43D8-978D-680D33946D96@kirei.se>

On 25 nov 2013, at 10:09, Sara Dickinson <sara at sinodun.com> wrote:

> As discussed in the team meeting last week the outstanding JIRA issues (330/436 - NSEC3PARAM TTL) have now been completed and so both the 1.3 and 1.4 branches are ready for the next patch releases. Please refrain from submitting any more code into either the 1.3 or 1.4 branch until after the releases unless you are sure it is safe to include in the production release. 
> 
> Jakob - since Jerry is on vacation could you please indicate if/when you could possibly create the release candidates for both these releases?

Yes, I can create release candidates tomorrow. 

	jakob

-- 
Jakob Schlyter
Kirei AB - www.kirei.se





From matthijs at nlnetlabs.nl  Wed Nov 27 12:15:39 2013
From: matthijs at nlnetlabs.nl (Matthijs Mekking)
Date: Wed, 27 Nov 2013 13:15:39 +0100
Subject: [Opendnssec-develop] Jenkins tests old revision
Message-ID: <5295E26B.2070702@nlnetlabs.nl>

Hi,

I want Jenkins to test the latest revision. The build seems to
automatically grab the latest change:

https://jenkins.opendnssec.org/job/build-opendnssec-1.3/280/
Revision: 7438
Changes

    fix memleak in libhsm (detail)


But the test takes an old one:

https://jenkins.opendnssec.org/job/test-opendnssec-1.3/310/
Revision: 7423
No changes.


How do I enforce Jenkins to test the latest revision?

Best regards,
  Matthijs


From sara at sinodun.com  Wed Nov 27 12:29:46 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 27 Nov 2013 12:29:46 +0000
Subject: [Opendnssec-develop] Jenkins tests old revision
In-Reply-To: <5295E26B.2070702@nlnetlabs.nl>
References: <5295E26B.2070702@nlnetlabs.nl>
Message-ID: <472E48DC-C01A-47B1-BBF3-6FB61B806282@sinodun.com>


On 27 Nov 2013, at 12:15, Matthijs Mekking wrote:

> Hi,
> 
> I want Jenkins to test the latest revision. The build seems to
> automatically grab the latest change:
> 
> https://jenkins.opendnssec.org/job/build-opendnssec-1.3/280/
> Revision: 7438
> Changes
> 
>    fix memleak in libhsm (detail)
> 
> 
> But the test takes an old one:
> 
> https://jenkins.opendnssec.org/job/test-opendnssec-1.3/310/
> Revision: 7423
> No changes.
> 
> 
> How do I enforce Jenkins to test the latest revision?


The jenkins jobs are configured up to look at a particular repository path: 
-  the build job grabs the code from  OpenDNSSEC/ and builds this (which has highest revision 7438)
-  however the test job grabs just the code from OpenDNSSEC/testing (which has highest revision 7423)

However the test job is running the tests against the latest build (which was generated by the build job) so it is using a build of 7438. Confusing I know, but I hope this helps.

Sara. 

From yuri at nlnetlabs.nl  Wed Nov 27 12:36:18 2013
From: yuri at nlnetlabs.nl (Yuri Schaeffer)
Date: Wed, 27 Nov 2013 13:36:18 +0100
Subject: [Opendnssec-develop] Jenkins tests old revision
In-Reply-To: <472E48DC-C01A-47B1-BBF3-6FB61B806282@sinodun.com>
References: <5295E26B.2070702@nlnetlabs.nl>
	<472E48DC-C01A-47B1-BBF3-6FB61B806282@sinodun.com>
Message-ID: <5295E742.7060907@nlnetlabs.nl>

> However the test job is running the tests against the latest build
> (which was generated by the build job) so it is using a build of
> 7438. Confusing I know, but I hope this helps.

Ah yes, so they are both up to date.
Doing the svn ci from the root of the repository would cause both jobs
have the same (latest) revision I believe.


-- 
Composed on an actual keyboard: all typos genuine.


From sara at sinodun.com  Wed Nov 27 15:58:20 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Wed, 27 Nov 2013 15:58:20 +0000
Subject: [Opendnssec-develop] RE: Migrating regression tests between 1.4 and
	2.0
Message-ID: <C5BF772A-4EBC-4B3E-BD77-243CC8E73AE6@sinodun.com>

Hi All, 

As part of trying to align the jenkins testing between 1.4 and 2.0 I have created a wiki page where I have made a brain dump of useful hints for porting tests and a list of issues I have seen when trying to get tests running:

https://wiki.opendnssec.org/display/OpenDNSSEC/Migrating+jenkins+regression+tests+between+1.4+and+2.0

This is a work in progress and seems like the best place to collect this information at the moment as I work through the tests in more detail! Please feel free to add to or correct the information here.

Sara. 

From sara at sinodun.com  Thu Nov 28 13:37:03 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 28 Nov 2013 13:37:03 +0000
Subject: [Opendnssec-develop] OpenDNSSEC 1.3.16rc1 release candidate
Message-ID: <1F1293FD-710E-4016-8CB3-09499688F93A@sinodun.com>

All, 

Version 1.3.16rc1 of OpenDNSSEC is now available. This is a release candidate for testing purposes:


OpenDNSSEC 1.3.16rc1
-----------------------------------

Updates:
* SUPPORT-72: Improve logging when failed to increment serial in case of key rollover and serial value "keep" [OPENDNSSEC-441].
* OPENDNSSEC-436: NSEC3PARAM TTL can now be optionally configured in kasp.xml. Default value remains PT0S.
* OPENDNSSEC-458: Add 'ods-enforcerd -p <policy>' option. This prompts the enforcer to run once and only process the specified policy and associated zones. 
* OPENDNSSEC-460: ods-ksmutil: Add an option to the 'ods-ksmutil key ds-seen' command so the user can choose not to notify the enforcer.
* OPENDNSSEC-472: ods-ksmutil: Add option for 'ods-ksmutil key import' to check if there is a matching key in the repository before import.
* OPENDNSSEC-473: ods-ksmutil: Improve 'zone add' - Support default <input> and <output> values for DNS adapters.

Bugfixes:
* OPENDNSSEC-451: Signer Engine: Prevent CKA_ID and DNSKEY mixup by using a separate HSM context when loading signer configuration.
* OPENDNSSEC-462: Signer Engine: Duration PT0S is not printed correctly.
* ods-ksmutil: Fix typo in policy export with NSEC3 <Iterations>.

Download: 
* http://dist.opendnssec.org/source/testing/opendnssec-1.3.16rc1.tar.gz
* http://dist.opendnssec.org/source/testing/opendnssec-1.3.16rc1.tar.gz.sig
* Checksum sha1: eea7d0ede9066f5dd65beeba775aafc4db98f592
* Checksum sah256: 5fa05df278932d0125dcb93efc3b08fa7adabea6867bec95ecf59af1e9349612


A full 1.3.16 release is planned for Wednesday 4th December. 

// OpenDNSSEC team



From sara at sinodun.com  Thu Nov 28 13:37:05 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Thu, 28 Nov 2013 13:37:05 +0000
Subject: [Opendnssec-develop] OpenDNSSEC 1.4.3rc1 release candidate
Message-ID: <66F0969D-DFBE-4ACD-BAAC-F0E004903265@sinodun.com>

All, 

Version 1.4.3rc1 of OpenDNSSEC is now available. This is a release candidate for testing purposes:


OpenDNSSEC 1.4.3rc1 
----------------------------------

Updates:
* SUPPORT-72: Improve logging when failed to increment serial in case of key rollover and serial value "keep" [OPENDNSSEC-461].
* OPENDNSSEC-106: Add 'ods-enforcerd -p <policy>' option. This prompts the enforcer to run once and only process the specified policy and associated zones.
* OPENDNSSEC-330: NSEC3PARAM TTL can now be optionally configured in kasp.xml. Default value remains PT0S.
* OPENDNSSEC-390: ods-ksmutil: Add an option to the 'ods-ksmutil key ds-seen' command so the user can choose not to notify the enforcer.
* OPENDNSSEC-430: ods-ksmutil: Improve 'zone add' - Zone add command could warn if a specified zone file or adapter file does not exits.
* OPENDNSSEC-431: ods-ksmutil: Improve 'zone add' - Support default <input> and <output> values for DNS adapters.
* OPENDNSSEC-454: ods-ksmutil: Add option for 'ods-ksmutil key import' to check if there is a matching key in the repository before import.

Bugfixes:
* OPENDNSSEC-435: Signer Engine: Fix a serious memory leak in signature cleanup.
* OPENDNSSEC-463: Signer Engine: Duration PT0S is now printed correctly.
* OPENDNSSEC-466: Signer Engine: Created bad TSIG signature when falling back to AXFR.
* OPENDNSSEC-467: Signer Engine: After ods-signer clear, signer should not use inbound serial.


Downloads:
* http://dist.opendnssec.org/source/testing/opendnssec-1.4.3rc1.tar.gz
* http://dist.opendnssec.org/source/testing/opendnssec-1.4.3rc1.tar.gz.sig
* Checksum sha1: ab62a1d224c86635617cfad74c59d2237605b1e4
* Checksum sha256: 42b97694b1fdef7b41929446b3939e4c5b34f4f029014d917d71ce20d40eee8d


A full 1.4.3 release is planned for Wednesday 4th December. 

//OpenDNSSEC team



From sara at sinodun.com  Fri Nov 29 15:41:45 2013
From: sara at sinodun.com (Sara Dickinson)
Date: Fri, 29 Nov 2013 15:41:45 +0000
Subject: [Opendnssec-develop] RE: Team meeting - Monday 2 Dec @ 14:00 CET
Message-ID: <4763D3D4-52AA-45DF-B5BF-B1B21299B20A@sinodun.com>

Hi All, 

We have a team meeting on *Monday* next week:

Date:      Monday 2 Dec 2013
Time:      14:00-15:00 CET, 13:00-14:00 GMT, 21:00-22:00 CST, 13:00-14:00 UTC
Method:  Teamspeak
Agenda:  https://wiki.opendnssec.org/display/OpenDNSSEC/2013-12-02+Agenda


Sara.