MRELEASE-128 SCM element properties replacement has been there for
long time. That would be nice to be fixed.
Rgds,
Markku
On 30.7.2010 2:01, Brett Porter wrote:
Several folks seem interested in a small handful of release plugin issues, so I
hoped to work on them next week and push towards g
Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
That's one on the list - it's already committed on trunk, and Olivier has
volunteered to help get the SCM release out :)
On 30/07/2010, at 7:39 AM, Mark Derricutt wrote:
> While not release plugin specific, there's a few Maven SCM issues which
> effect the release process when using git.
>
> On
+1 to release Maven SCM too
See http://jira.codehaus.org/browse/MRELEASE-497 and
http://jira.codehaus.org/browse/SCM-562
On Fri, Jul 30, 2010 at 3:39 AM, Mark Derricutt wrote:
> While not release plugin specific, there's a few Maven SCM issues which
> effect the release process when using git.
>
While not release plugin specific, there's a few Maven SCM issues which
effect the release process when using git.
One of the mains ones being http://jira.codehaus.org/browse/SCM-444 - which
provides functionality to disable a git push during release:prepare.
If we're doing a release of the relea
Several folks seem interested in a small handful of release plugin issues, so I
hoped to work on them next week and push towards getting another release out.
Are there any issues that folks here would like to work on and see included
that aren't already?
Cheers,
Brett
--
I don't know what Kristian is doing with weave mode, but the logging will most
likely be fixed by the use of Guice, and Benjamin can answer you about the IT.
On Jul 29, 2010, at 5:58 PM, Paul Benedict wrote:
> But what about the remaining 3 issues? Are they going into the next release
> or being
But what about the remaining 3 issues? Are they going into the next release
or being pushed off?
On Thu, Jul 29, 2010 at 10:00 AM, Jason van Zyl wrote:
> Next week-ish.
>
> On Jul 29, 2010, at 10:56 AM, Paul Benedict wrote:
>
> > What is the plan to release the next beta? The open issues have pr
I think it is but I'll check tomorrow
On 29 July 2010 19:09, Paul Gier wrote:
> I'd like to get out the next release of surefire and related
> plugins/components, and just wanted to check on the status of the
> remaining open issues.
>
> Stephen, is the refactoring work from SUREFIRE-592 in a st
I'd like to get out the next release of surefire and related
plugins/components, and just wanted to check on the status of the
remaining open issues.
Stephen, is the refactoring work from SUREFIRE-592 in a stable state?
The remaining issues look like they can be pushed to a future release.
-
On Jul 29, 2010, at 11:04 AM, Paul Benedict wrote:
> Jason and all,
>
> Would you be interested in extra help by me being a backup release manager?
No, we're fine thanks. We like doing the releases so we stay intimately
acquainted with the tools. It's pretty much automated at this point anyway
Jason and all,
Would you be interested in extra help by me being a backup release manager?
I don't have the time this month, but I could do it sometime later this
year. If you have instructions on the web, I can follow those. I already do
this for Struts so I am not green on the Apache procedures.
Next week-ish.
On Jul 29, 2010, at 10:56 AM, Paul Benedict wrote:
> What is the plan to release the next beta? The open issues have pretty much
> quieted down and the remaining three don't have recent activity. Is the
> Release Manager planning to resolve these in Beta 2 or push them to Beta 3?
>
What is the plan to release the next beta? The open issues have pretty much
quieted down and the remaining three don't have recent activity. Is the
Release Manager planning to resolve these in Beta 2 or push them to Beta 3?
Paul
14 matches
Mail list logo
