incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Haywood <dkhayw...@gmail.com>
Subject Re: A modest suggestion about testing versus release votes
Date Wed, 06 Jul 2011 07:18:39 GMT
Thanks Nour, but this is pretty much the documented process already [1], 
though (1.1) is different ... we do the release from a branch, and 
reintegrate once the vote is passed.

[1] 
http://incubator.apache.org/isis-0.1.2-incubating/docbkx/html/guide/ch12.html


On 05/07/2011 19:40, Mohammad Nour El-Din wrote:
> To brief what Benson suggested and to put it into steps we can do the following:
>
> 1- Declare the intention of preparing a release
>    1.1- Stop committing new changes to trunk
>    1.2- Make primary tests for building from source and running unit tests
>    1.3- Making sure that all features addressed for that release are
> done and bugs are solved
>    1.4- If new bugs which can block the release are found, then we
> start again from step 1.2
>
> 2- Produce the release artifacts
>    2.1- Given the steps in section (1) are completed as described
> above, this step is mainly to make sure that produced release
> artifacts hold the
>           criteria required by ASF.
>    2.2 If problems found, we cut a new release and we keep do till we
> produce _the_ release candidate with which we can go to the general@.
>
> Thoughts ?
>
> On Tue, Jul 5, 2011 at 3:57 PM, Benson Margulies<bimargulies@gmail.com>  wrote:
>> Right. And my point is, using the release process as the primary QA
>> driver makes a lot of extra work for you. It's just messy to be
>> getting bug reports and deciding what to do about them off of a vote
>> thread.
>>
>> On Tue, Jul 5, 2011 at 9:12 AM, Mohammad Nour El-Din
>> <nour.mohammad@gmail.com>  wrote:
>>> +1
>>>
>>> More specifically we are still getting used to the release process.
>>>
>>> On Tue, Jul 5, 2011 at 2:39 PM, Benson Margulies<bimargulies@gmail.com>
 wrote:
>>>> Might I suggest some sort of informal testing process *before* you
>>>> call a vote? Go ahead, if you like, and stage XXX-RC-1 to nexus, but
>>>> don't call a vote. Get people to test it and find problems like broken
>>>> links and missing notices. When it all looks clean, just drop the
>>>> staged repo, and run the release with the actual release version. Then
>>>> your votes can look like 95% of all the other votes at apache; a
>>>> pretty rapid verification process.
>>>>
>>>
>>>
>>> --
>>> Thanks
>>> - Mohammad Nour
>>>    Author of (WebSphere Application Server Community Edition 2.0 User Guide)
>>>    http://www.redbooks.ibm.com/abstracts/sg247585.html
>>> - LinkedIn: http://www.linkedin.com/in/mnour
>>> - Blog: http://tadabborat.blogspot.com
>>> ----
>>> "Life is like riding a bicycle. To keep your balance you must keep moving"
>>> - Albert Einstein
>>>
>>> "Writing clean code is what you must do in order to call yourself a
>>> professional. There is no reasonable excuse for doing anything less
>>> than your best."
>>> - Clean Code: A Handbook of Agile Software Craftsmanship
>>>
>>> "Stay hungry, stay foolish."
>>> - Steve Jobs
>>>
>
>

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message