I think this is all set to go - sorry for the delay!
Let me know if there's more I can do to help with the release process...
On 20/01/2010, at 6:56 AM, Dennis Lundberg wrote:
> Okay, we're now down to 0 issues left in JIRA for a 2.0 release.
>
> Does anybody have anything more they want to add
Ok, I found another issue with the flat multi-module capabilities
(MRELEASE-261), and I've placed MRELEASE-3 in the 2.0 bucket with the intent to
do the plan below. I have the first mostly fixed with a test in place, so I
intend to get these resolved later tonight / early tomorrow so that Dennis
On 20/01/2010, at 6:56 AM, Dennis Lundberg wrote:
> Okay, we're now down to 0 issues left in JIRA for a 2.0 release.
>
> Does anybody have anything more they want to add before I start the
> release process?
It's getting late here, so I'll have to investigate this further tomorrow, but
I think
Brett Porter schrieb:
As the resolution is only needed for the release poms which are off by default,
in hindsight I don't think we should have added it. Would the following be
workable?
1) Remove the resolution tag from prepare
2) Add a new mojo :prepare-full, that extends prepare and adds th
On 20/01/2010, at 6:56 AM, Dennis Lundberg wrote:
> Okay, we're now down to 0 issues left in JIRA for a 2.0 release.
>
> Does anybody have anything more they want to add before I start the
> release process?
I fixed up a test failure on Windows.
I got bitten by this again this week, so I'd like
Okay, we're now down to 0 issues left in JIRA for a 2.0 release.
Does anybody have anything more they want to add before I start the
release process?
Dennis Lundberg wrote:
> Hi
>
>
> I'm currently looking at what is needed to release the Release Plugin.
>
>
> There are 5 issues left in JIRA,
Dennis Lundberg wrote:
Which of these do we intend to fix and which can be bumped to the next
version?
Personally, I don't see much value in having an issue scheduled for some
release when nobody has actually time/interest to work on it, thereby
blocking a release. Go for as much as you can
Hi,
Personnaly, I'm tempted to move as "Won't Fix" : MRELEASE-449 and MRELEASE-450.
Regarding MRELEASE-83, I don't really understand why -Dusername
doesn't work (it should :-) ).
Scm 1.3, I will try to do this ASAP (if enough spare time this week)
Concerning MRELEASE-261, this need more tests su
release the Release Plugin
Hi
I'm currently looking at what is needed to release the Release Plugin.
There are 5 issues left in JIRA, of the 29 issues that are scheduled for
2.0-beta-10:
http://jira.codehaus.org/browse/MRELEASE-449
Parent snapshot version is not rewritten to resolve
Hi
I'm currently looking at what is needed to release the Release Plugin.
There are 5 issues left in JIRA, of the 29 issues that are scheduled for
2.0-beta-10:
http://jira.codehaus.org/browse/MRELEASE-449
Parent snapshot version is not rewritten to resolved non-snapshot
version during release:
10 matches
Mail list logo