couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <...@apache.org>
Subject Re: Releases procedure
Date Thu, 21 Feb 2013 17:59:34 GMT

On Feb 21, 2013, at 18:41 , Noah Slater <nslater@apache.org> wrote:

> The hours and days I am spending on this release are trying to make up for
> a non-deterministic test suite that can take hours and hours to babysit, to
> the point where I am having to automate my way around it.

I still haven’t seen any logs that I could use to help debug this.

> 
> The NEWS and CHANGES stuff should take 5-10 minutes tops. But if it is
> neglected, then the problem compounds, because now I have to look through
> the timelines and organise things so we are consistent.
> 
> 
> On 21 February 2013 17:32, Jan Lehnardt <jan@apache.org> wrote:
> 
>> 
>> On Feb 21, 2013, at 18:29 , Noah Slater <nslater@apache.org> wrote:
>> 
>>> Your response rests on a fallacy, in any case.
>>> 
>>> Maintaining a list of release versions is going to be a PITA no matter
>> what
>>> we do. Especially when we have four or five divergent timelines. Moving
>>> these to the docs only consolidates the maintenance into one file. This
>>> will still require care and attention, and I believe it is appropriate of
>>> me to remind people of that. The current state of affairs is a complete
>>> mess.
>> 
>> All I know is we spend hours and days on this each release and I don’t
>> think this needs to be the case.
>> 
>> Best
>> Jan
>> --
>> 
>> 
>> 
>>> 
>>> 
>>> On 21 February 2013 17:19, Jan Lehnardt <jan@apache.org> wrote:
>>> 
>>>> 
>>>> On Feb 21, 2013, at 18:16 , Noah Slater <nslater@apache.org> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> If you're doing a release, please ensure proper NEWS and CHANGES
>> hygiene
>>>>> The recent releases went out with a entries in these files for versions
>>>> we
>>>>> have not yet released. And some are missing entries for previous
>> versions
>>>>> we have released. I have added a few additional instructions to the
>> wiki,
>>>>> so hopefully these will be caught next time.
>>>> 
>>>> Alternatively, let’s finally kill this superfluous, error-prone,
>>>> time-wasting
>>>> distraction from actual work and ensure the important information
>> contained
>>>> in it are covered in the docs.
>>>> 
>>>> Cheers
>>>> Jan
>>>> --
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> NS
>> 
>> 
> 
> 
> -- 
> NS


Mime
View raw message