+1
The value is in the process, and that comes from it being simple and
repeatable, minimising 'specials' :)
-Chris
On Sun, Dec 15, 2013 at 2:26 AM, Robert Scholte wrote:
> +1 for a standardized process, even though the results for mono-projects
> stay the same.
>
> Robert
>
> Op Sat, 14 Dec 201
+1 for a standardized process, even though the results for mono-projects
stay the same.
Robert
Op Sat, 14 Dec 2013 15:47:51 +0100 schreef Hervé BOUTEMY
:
the only change is that you'd have to run "mvn -Preporting site
site:stage"
even for mono-modules, when actually the "site:stage" part
the only change is that you'd have to run "mvn -Preporting site site:stage"
even for mono-modules, when actually the "site:stage" part is required only
for multi-module
the purpose is to have stupid easy unified instructions, without "if multi-
module" step: every component has the exact same co
Could you describe in short how the process would look like? As in
staging/performing the release and finalizing it (after enough votes).
Robert
Op Sat, 14 Dec 2013 14:19:52 +0100 schreef Hervé BOUTEMY
:
before I update documentation and parent poms:
any objection from any future release
before I update documentation and parent poms:
any objection from any future release manager if we unify site:stage
requirement?
Regards,
Hervé
Le mardi 10 décembre 2013 23:59:19 Hervé BOUTEMY a écrit :
> really, here is the link...
> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-
