+1 to release as soon as possible.
As discussed in the other thread, I also think the package rename
should be delayed until 2.0.
Regarding the Chef thing, I am open to whatever is preferred. It is
very stable and can be merged without issues in the main repo, but I
don't think this should be a
Yup, mentioned in the wiki.
Doh, sloppy reading, sorry. It didn't render properly for me, I think
(see attachment) - should be fixed now [1]?
ap
[1]
https://wiki.apache.org/jclouds/Releasing%20jclouds?action=diffrev1=27rev2=28
On Thu, Nov 14, 2013 at 10:18:02AM -0800, Andrew Bayer wrote:
So with 1.6.3 aiming to be out next week, I'd like to put a target date on
1.7.0 - we really need to get that sucker out! I'm gonna tentatively plan
to do the first RC on Monday, December 9th.
There are a fair number of issues
Should we publish 1.7 alpha/beta artifacts like we did pre-ASF? Ideally
we would have done this regularly during the 1.7 development cycle.
If we can find a way to do this reasonably quickly (ideally,
automatically!) I'm sure that would help. As it is (hope it's been
smooth for you, Andrew
Should we publish 1.7 alpha/beta artifacts like we did pre-ASF? Ideally
we would have done this regularly during the 1.7 development cycle.
...
Would work for me - they've been stable for ages, see active use and
improvements and don't feel significantly less generic that e.g.
route53.
ap
I
Just did a bit of cleanup on the 1.6.x branch of jclouds-labs-openstack to
get its versioning in a sane way - turns out the sane way was already in
place for 1.7.0 there, so woo. Checking the others now, but I think we're
ok with an extra step I specified on the release process wiki.
Do we need
On Nov 14, 2013, at 12:18 PM, Andrew Bayer wrote:
So with 1.6.3 aiming to be out next week, I'd like to put a target date on
1.7.0 - we really need to get that sucker out! I'm gonna tentatively plan
to do the first RC on Monday, December 9th.
+1
Everett
+1
Best,
Alex
On Nov 15, 2013 4:22 PM, Everett Toews everett.to...@rackspace.com
wrote:
On Nov 14, 2013, at 12:18 PM, Andrew Bayer wrote:
So with 1.6.3 aiming to be out next week, I'd like to put a target date
on
1.7.0 - we really need to get that sucker out! I'm gonna tentatively plan
So with 1.6.3 aiming to be out next week, I'd like to put a target date on
1.7.0 - we really need to get that sucker out! I'm gonna tentatively plan
to do the first RC on Monday, December 9th.
There are a fair number of issues still open against 1.7.0 - see
Sounds good to me.
I'd really like to have the issue (don't remember the id) to configure the
versioning in the sub-repos completed for 1.7.
It has been done in several repos but not in all of them (at least
jclouds-labs is still remaining), and I think it is important that we have
a consistent
I believe you're talking about
https://issues.apache.org/jira/browse/JCLOUDS-141 and
https://issues.apache.org/jira/browse/JCLOUDS-104?
A.
On Thu, Nov 14, 2013 at 12:10 PM, Ignasi ignasi.barr...@gmail.com wrote:
Sounds good to me.
I'd really like to have the issue (don't remember the id) to
...@rackspace.com wrote:
Is there a short overview of what the current plan is? Is it 141?
From: Andrew Bayer [andrew.ba...@gmail.com]
Sent: Thursday, November 14, 2013 2:17 PM
To: dev@jclouds.apache.org
Subject: Re: 1.7.0 scheduling
I believe you're talking
12 matches
Mail list logo
