maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Rosenvold <kristian.rosenv...@gmail.com>
Subject Re: Change request procedure that spans multiple projects
Date Thu, 09 Jan 2014 11:34:53 GMT
Technically there should be separate *issues* no matter what, since
deciding how to *release* is typically a different process.

Kristian


2014/1/9 Stephen Connolly <stephen.alan.connolly@gmail.com>

> Well plexus is a separate (although related) community. We certainly can
> combine the vote thread for the maven community components, and we have
> done so in the past... just a question of the release manager deciding that
> they are fine coupling the releases of multiple components in one vote.
>
>
> On 9 January 2014 10:27, Barrie Treloar <baerrach@gmail.com> wrote:
>
> > On 9 January 2014 17:37, Kristian Rosenvold
> > <kristian.rosenvold@gmail.com> wrote:
> > > Create one jira ticket for each project and create a 'depends on' link
> > > between the issues.
> >
> > I think there was talk about voting to release the lot as a bundle but
> > I've not done that - you might search the archive for it.
> > The other way is just release them one at a time and in the correct
> > order once you've fixed the problems.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>

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