My time might be quite limited these days, but with a lot of patience from the mentors I can help releasing if needed.
On 16 May 2013 17:43, Adrian Cole <[email protected]> wrote: > I think we can have our cake and eat it too by doing both in ASF. We are > already publishing snapshots on 1.6.x. I can vouch that at least the core > ones work. We don't need to compromise when things actually work. I > understand we have steps to do, but unlike many incubator projects, we have > several active committers and mentors. Of all projects, we should have a > fair chance of getting things together. > > Even if folks wanted to do a non-ASF 1.6.1 release, it probably isn't > appropriate to plan it on this list, and we wouldn't be able to announce it > on this list. I remember cloudstack being scolded about non-ASF release > discussions, and would like to avoid that here. > > -A > > > On Thu, May 16, 2013 at 8:38 AM, Andrew Phillips <[email protected]>wrote: > >> I'm not really available for the next week - we still need to do license >>> header updates to ASF, at a minimum, and I'd like to have the ASF web page >>> etc all up before we do our first release. Let's aim at, say, mid-June? >>> >> >> Could we "try to have our cake and eat it" by targeting the ASF stuff for >> the 1.7.0 release and doing 1.6.1 (as a minor release) before that? >> >> Or would that be regarded as not following the correct procedure? >> Especially as we have already made some changes, e.g. org.jclouds -> >> org.apache.jclouds, also on the 1.6.x branch... >> >> ap >>
