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 Mon, 03 May 2010 18:47:13 GMT
2010/5/3 Mck <mick@semb.wever.org>:
>  Instead when a release is made part of the release process is to bulk
> transit all resolved issues over to closed.
>  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.

>> > ... That is after tiles-master is (voted and)
>> > released to version 2 then the other pom files must be updated and
>> > committed. Only then the website will have correct links to the
>> > issue-tracker?
>> Not necessarily. If you like, you can deploy a snapshot (mvn deploy),
>> let the other project depend on the snapshot
> I'm not very fond of inheriting from SNAPSHOT parents. Apart from the
> project instability it introduces it also slows down every build.

Ok for the instability, but it is resolved when it is released thanks
to the Maven release plugin that checks the presence of snapshots.
About the slowdown, what do you mean? I don't think it is so tragic,
and you can still build offline.


View raw message