[Opendnssec-develop] RE: 1.3.12 release candidate

[Sara Dickinson]

On 10 Dec 2012, at 10:41, Matthijs Mekking wrote:

> We could also 'tag' the release candidate. Tagging means making no
> changes to them. If changes are required, they are made in the branch.
> If changes are made, a new rc is created from branch. Advantages: No
> need for merging and no need to freeze the branch.
> 

On other products I have worked on the only changes allowed between an RC and full release were fixes to issues found with the RC (e.g. build issues or a critical bug fix that didn't work properly).  Nothing 'new' was allowed in even if the RC was re-issued. 

Doing what you suggest means that if someone puts a fix in the branch for something that wasn't in the original RC and then you need a new RC for some reason, then that new fix ends up in the new RC..... Also the danger is that the new fix breaks something, or you have to wait for it to be tested, etc. and the release is delayed again.... 

Sara.


> Best regards,
>  Matthijs
> 
> On 12/10/2012 11:38 AM, Sara Dickinson wrote:
>> Hi Jerry, 
>> 
>> It is a good point that it isn't necessary but based on discussions in the team meetings and the fact it has been documented as part of the process for some time now I took this as what we had agreed to do.
>> 
>> We could alternatively do as suggested below however I would not vote in favour of this. I prefer freezing the branch as it is a much simpler approach and is less error prone than having to merge changes. I would suggest we continue with the current process and if we do find it to be an issue then we could review things. However if others feel differently then please speak up! 
>> 
>> Sara.
>> 
>> On 10 Dec 2012, at 07:55, Jerry Lundström wrote:
>> 
>>> Hi,
>>> 
>>> On Mon, Nov 26, 2012 at 3:05 PM, Sara Dickinson <sara at sinodun.com> wrote:
>>>> Since we have a release candidate issued please refrain from submitting routine code into the 1.3.12 branch until the full release is done. If you have a high priority issue that you believe warrants the re-issue of the release candidate please email the developers list first so this can be agreed.
>>> 
>>> It isn't necessary to "lock" the branch while a release candidate is issued.
>>> 
>>> You can copy the release candidate tag once it is decided to release
>>> the full version and if any change had been made that should be
>>> included in the release you can merge it with the release tag after
>>> copy.
>>> 
>>> -- 
>>> 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