On 4/20/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
What do you guys think? just call a vote on it and get it pushed into
the wild or can we just do the alpha's like this through the staging
setup?
The vote makes it an official release tha can be annouced on the user
list. Whether to put i
might as well just use this thread...
I have continuum 1.1 alpha 1 staged now...but I have one concern about
calling a vote on this and making it official...
Its kinda big (16M war, 25M plexus app) and I still don't really feel
comfortable releasing something like continuum as an alpha into the
I'm ok for a timestamped version, but we can release the release manager too,
without the plugin because it isn't ready and I want the new Maven-SCM in it.
The pb is that release-manager use maven-scm 1.0-SNAPSHOT, we can use 1.0-beta-4 because the release manager doesn't use new code of maven-s
with maven-app-configuration released I thought we were well on our
way to getting a release of continuum cut, but Emmanuel pointed out
that I had missing the latest SNAPSHOT of the maven release stuff.
Does anyone have an issues with my resolving the maven-release version
to the latest timestamp
All outstanding jira tickets that were under 1.1-alpha-1 have been resolved...
I am going to put together the dependencies that need to be released
and get those on track for release now and then we can stage and call
a vote on the first alpha of continuum 1.1
jesse
On 3/20/07, Brett Porter <[E
On 20/03/2007, at 6:45 AM, Jesse McConnell wrote:
ok, I am changing my tune on the remaining 11 issues, I want this
thing released asap so we have something concrete to get moving on.
The 11 issues are functionally no real different then a lot of the
ones in the -2 jira so I am thinking we just
for what my opinion matters, I'm in favor of the bi-weekly schedule.
On 3/19/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
ok, I am changing my tune on the remaining 11 issues, I want this
thing released asap so we have something concrete to get moving on.
The 11 issues are functionally no rea
ok, I am changing my tune on the remaining 11 issues, I want this
thing released asap so we have something concrete to get moving on.
The 11 issues are functionally no real different then a lot of the
ones in the -2 jira so I am thinking we just push that forward and get
going on this.
so, I have
yes, you are also correct on that, great point
On 3/15/07, Thierry Lach <[EMAIL PROTECTED]> wrote:
Of the unresolved issues for 1.1-alpha-any, 108 of them are against some
version of continuum 1.0 and might not apply to continuum-1.1, but someone
is going to have to verify that.
On 3/13/07, Bre
Of the unresolved issues for 1.1-alpha-any, 108 of them are against some
version of continuum 1.0 and might not apply to continuum-1.1, but someone
is going to have to verify that.
On 3/13/07, Brett Porter <[EMAIL PROTECTED]> wrote:
On 12/03/2007, at 7:35 AM, Jesse McConnell wrote:
On 13/03/2
On 3/13/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
to be perfectly honest, I think there are a number of smelly parts
inside of continuum right now, I have worked out designs and written
mails on the subject a number of times to this list, but I haven't had
the time to just sit down and fix t
On 3/13/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
A bit of (constructive) criticism ahead
These are the numbers I see in jira right now
1.1-alpha-1 11
1.1-alpha-2 72
1.1-alpha-# 156
that is correct, and I frankly don't think there is a hill of beans
chance of resolving all of
A couple of things:
1. Once the first alpha is released, why not try to put a new one out
there every week or every two weeks? Anything scheduled for the alpha-2
release (for example) that isn't done could be moved back to alpha-3, and so
on.
2. I'd love to be able to try to provide m
On 3/13/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> do we want to release the final 1.1 in 2050?
I think you might need to help with the definition of 'constructive'
criticism :)
it's just my english that is badly :p
> This is how it looks to me from outside, as I didn't have time lately
On 12/03/2007, at 7:35 AM, Jesse McConnell wrote:
having to resolve the snapshot dependencies are precisely the reason I
didn't want to mess with the maven release plugin for this. I would
have to release a new plexus-security and probably a couple of other
little higgly piggly bits. I think
A bit of (constructive) criticism ahead
On 3/9/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
I have gone through jira issues there were assigned to 1.1 and spread
things out a bit.
here is my criteria I used in separating out the issues:
1.1-alpha-1 -> issues that need to be addressed asap be
Jesse McConnell wrote:
> I think we shouldn't worry about making these actually releases cut
> with the maven-release-plugin. I say we just make a build and get it
> available for download. Also tag the continuum trunk accordingly.
> Then we ought to try to release a new alpha every few weeks u
Jesse McConnell wrote:
sounds good to me, imo either trunc it or maybe switch the model over
to a clob for that in the db...
I tried to make it a CLOB once but couldn't get it to work because of
some JPOX issues IIRC so for alpha-1 just chop the exception and/or
write it to a separate file an
Jesse McConnell wrote:
I have gone through jira issues there were assigned to 1.1 and spread
things out a bit.
here is my criteria I used in separating out the issues:
1.1-alpha-1 -> issues that need to be addressed asap before we pull
any kinda alpha
1.1-alpha-2 -> higher importance issues and
sounds good to me, imo either trunc it or maybe switch the model over
to a clob for that in the db...
jesse
On 3/9/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
On 3/9/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
> I have gone through jira issues there were assigned to 1.1 and spread
> thing
On 3/9/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
I have gone through jira issues there were assigned to 1.1 and spread
things out a bit.
here is my criteria I used in separating out the issues:
1.1-alpha-1 -> issues that need to be addressed asap before we pull
any kinda alpha
Not becaus
I have gone through jira issues there were assigned to 1.1 and spread
things out a bit.
here is my criteria I used in separating out the issues:
1.1-alpha-1 -> issues that need to be addressed asap before we pull
any kinda alpha
1.1-alpha-2 -> higher importance issues and ones generally related
22 matches
Mail list logo
