Regardless of these process issues, I should add that I'm all for
getting a release out. Congrats to the team on feeling things are
stable enough to go out and thanks for all the hard work put into
other areas of the project.
Brian
On Jan 11, 2007, at 9:30 AM, Brian Topping wrote:
I'm in a similar situation with patches I've provided. Some have
integration tests as well, as requested. No comments have been
made on any of the patches, they are months old.
They might not seem important, but we had to throw away our entire
Maven investment at a company I am at, after months of work to get
it integrated and create these patches when problems developed. A
primary reason for it's demise was people didn't like using forked
builds of Maven just so they could get their daily work done.
[-1]. The process should be updated so patches are either rejected
with corrective measures or given a "fix version" where they will
be applied.
Brian
On Jan 11, 2007, at 2:04 AM, Franz Fehringer wrote:
Hello,
WAGONHTTP-6 and MNG-2066 are already resolved; the fixes only need
to be incorporated in the 2.0.5 (or 2.0.6) release.
MNG-2305 should then also be resolved.
Greetings
Franz
Tom Huybrechts schrieb:
Can't you "solve" this with -Dhttps.proxyHost=xxx -
Dhttps.proxyPort=... ?
On 1/11/07, Franz Fehringer <[EMAIL PROTECTED]> wrote:
Will this release contain solutions to
MNG-2305
MNG-2066
WAGONHTTP-6
?
These issues mean, that it is impossible to access HTTPS (SSL)
repositories from behind proxies/firewalls (i.e. from corporate
networks).
Thanks and greetings
Franz
Jason van Zyl schrieb:
> Hi,
>
> I want to call a vote for 2.0.5. All the issues that are going
to get
> done are done. We'll release and move on.
>
> I would like to start building all releases from a standard
machine
> with the same JDK. I would like to propose the maven.org
machine which
> is monitored 24/7 running Linux. It serves as the central
repository
> but can easily handle a few builds. They can be built from that
> machine and deployed to Apache. I think this is far better
then each
> of us building stuff from our own machines and deploying.
>
> Otherwise everything for 2.0.5 is ready to go.
>
> I will also chop up what's in JIRA into some smaller versions
as I
> think some micro releases for improvements and smaller changes is
> better then waiting 7 months for another release. If we
schedule them
> out them people can decide whether they want to upgrade or
not. But I
> know there are several things I would like to get in and I
know that
> Mike/Ralph would like to get in MNG-1577 which we can squeeze
into a
> 2.0.6 in a week or two. These are micro release.
>
> Jason.
>
>
-------------------------------------------------------------------
--
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
