tiles-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Petrelli <antonio.petre...@gmail.com>
Subject Re: [jira] Commented: (TILES-506) Fix link to jira under "Project Information --> Issue tracking"
Date Tue, 04 May 2010 07:35:58 GMT
2010/5/4 Mck <mick@semb.wever.org>:
>
>> >  In this manner the release process itself substitutes as the quality
>> > assurance.
>>
>> In fact, in the early days of Tiles we did like this, but, in fact,
>> the "resolved" state is still without meaning.
>> Suppose that a build fails, you have to declare the version "invalid"
>> and move all the issues to another version. This step is needed even
>> if you use "resolved" state.
>
> I don't quite understand you.
> In this context what do you mean the "build failed" ?

I used the wrong term, sorry. I meant "leave as a test build". A long
time ago we voted against a test build because it did not contain
javadocs.

> And why would the
> issue be invalid?

Not the issue, the version in the "Fix for" field of Jira issues. The
issues should be moved to a higher version.
A thing that you might not have noticed is that we adopted an "always
increase" build numbers. We do not use RC, Beta etc. in version
numbers. We use X.Y.Z scheme plus a judgment about its
maturity/stability (Alpha, Beta, GA, only a test build).

Sorry if I've not been clearer before, but after several years here
I've taken for granted some things that might not be clear for new
people.
Anyway, your questions are always welcome!

Antonio

Mime
View raw message