You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Noah Slater <ns...@apache.org> on 2013/02/21 18:16:49 UTC
Releases procedure
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.
Thanks,
--
NS
Re: Releases procedure
Posted by Noah Slater <ns...@apache.org>.
Actually, looking at the NEWS and CHANGES on 1.2.1, 1.0.4, 1.1.2, 1.2.0,
and master... The whole thing is in a complete mess. It's going to take
some time to sort this out. Which we'd have to do before we got this in our
docs anyway.
On 21 February 2013 17:19, Jan Lehnardt <ja...@apache.org> wrote:
>
> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
Re: Releases procedure
Posted by Noah Slater <ns...@apache.org>.
I will do when my scripts are producing them. I think Bob is looking at
trying to replicate.
On 21 February 2013 18:12, Jan Lehnardt <ja...@apache.org> wrote:
> Hey Noah, sorry for being snipey.
>
> On Feb 21, 2013, at 19:07 , Noah Slater <ns...@apache.org> wrote:
>
> > I know. I've been busy working on my automation.
> >
> > Steps to reproduce:
> >
> > Spin up an xlarge Ubuntu AMI. Use most recent supported Ubuntu in quick
> > launch wizard. (ami-640a0610)
> >
> > Try "make distsign"
> >
> > That's it.
>
> Would be awesome if someone could send failure logs here.
>
> Cheers
> Jan
> --
>
>
> >
> >
> > On 21 February 2013 17:59, Jan Lehnardt <ja...@apache.org> wrote:
> >
> >>
> >> On Feb 21, 2013, at 18:41 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
> >>>
> >>>>
> >>>> On Feb 21, 2013, at 18:29 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
> >>>>>
> >>>>>>
> >>>>>> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
> >>
> >>
> >
> >
> > --
> > NS
>
>
--
NS
Re: Releases procedure
Posted by Jan Lehnardt <ja...@apache.org>.
Hey Noah, sorry for being snipey.
On Feb 21, 2013, at 19:07 , Noah Slater <ns...@apache.org> wrote:
> I know. I've been busy working on my automation.
>
> Steps to reproduce:
>
> Spin up an xlarge Ubuntu AMI. Use most recent supported Ubuntu in quick
> launch wizard. (ami-640a0610)
>
> Try "make distsign"
>
> That's it.
Would be awesome if someone could send failure logs here.
Cheers
Jan
--
>
>
> On 21 February 2013 17:59, Jan Lehnardt <ja...@apache.org> wrote:
>
>>
>> On Feb 21, 2013, at 18:41 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
>>>
>>>>
>>>> On Feb 21, 2013, at 18:29 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
>>>>>
>>>>>>
>>>>>> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
>>
>>
>
>
> --
> NS
Re: Releases procedure
Posted by Noah Slater <ns...@apache.org>.
I know. I've been busy working on my automation.
Steps to reproduce:
Spin up an xlarge Ubuntu AMI. Use most recent supported Ubuntu in quick
launch wizard. (ami-640a0610)
Try "make distsign"
That's it.
On 21 February 2013 17:59, Jan Lehnardt <ja...@apache.org> wrote:
>
> On Feb 21, 2013, at 18:41 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
> >
> >>
> >> On Feb 21, 2013, at 18:29 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
> >>>
> >>>>
> >>>> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
>
>
--
NS
Re: Releases procedure
Posted by Jan Lehnardt <ja...@apache.org>.
On Feb 21, 2013, at 18:41 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
>
>>
>> On Feb 21, 2013, at 18:29 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
>>>
>>>>
>>>> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
Re: Releases procedure
Posted by Noah Slater <ns...@apache.org>.
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.
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 <ja...@apache.org> wrote:
>
> On Feb 21, 2013, at 18:29 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
> >
> >>
> >> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
Re: Releases procedure
Posted by Jan Lehnardt <ja...@apache.org>.
On Feb 21, 2013, at 18:29 , Noah Slater <ns...@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 <ja...@apache.org> wrote:
>
>>
>> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
Re: Releases procedure
Posted by Noah Slater <ns...@apache.org>.
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.
On 21 February 2013 17:19, Jan Lehnardt <ja...@apache.org> wrote:
>
> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
Re: Releases procedure
Posted by Noah Slater <ns...@apache.org>.
This is an unhelpful response. We have already spoken about this, and
agreed this is the way forward.
However, for now, as long as this is our actual system, we need to maintain
it. The 1.1.2 release went out without the section being updated at all, it
seems.
https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob_plain;f=NEWS;hb=1d2a7d9bc93fc68384c0d7c4f4c40fcc74b7768c
On 21 February 2013 17:19, Jan Lehnardt <ja...@apache.org> wrote:
>
> On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
Re: Releases procedure
Posted by Jan Lehnardt <ja...@apache.org>.
On Feb 21, 2013, at 18:16 , Noah Slater <ns...@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
--