Re: Let's cut a Nano release

I'm happy to provide another PR to clean up the package.json. Currently we have developers providing fixes to the dscape/nano project (the original source of this project). It would be preferable if - nano's package.json pointed to https://github.com/apache/couchdb-nano - dscape/nano's readme

Re: Let's cut a Nano release

Should i move the repo? Happy to help in whatever capacity is required, I never really understood the full cycle here. Please provide instructions if need be, happy to do it On Thu, Oct 27, 2016 at 10:56 AM Garren Smith wrote: > Hi All, > > I want to follow up with this.

Re: Let's cut a Nano release

Hi All, I want to follow up with this. How is nano being managed? It seems that dscape/nano is being updated with new fixes where as couchdb-nano is being left alone. Glynn has a pull request to update couchdb-nano ( https://github.com/apache/couchdb-nano/pull/1) and bring it up to date. He also

Re: Let's cut a Nano release

Does this stop us from cutting a release? Best Jan -- > On 06 Dec 2015, at 23:50, Robert Kowalski wrote: > > Hi I got sad news: > > https://issues.apache.org/jira/browse/INFRA-10252 > > On Fri, Sep 18, 2015 at 4:43 PM, Jan Lehnardt wrote: >> Great stuff,

Re: Let's cut a Nano release

Few months is still better than never. So it's good news (: -- ,,,^..^,,, On Mon, Dec 7, 2015 at 1:50 AM, Robert Kowalski wrote: > Hi I got sad news: > > https://issues.apache.org/jira/browse/INFRA-10252 > > On Fri, Sep 18, 2015 at 4:43 PM, Jan Lehnardt

Re: Let's cut a Nano release

Hi I got sad news: https://issues.apache.org/jira/browse/INFRA-10252 On Fri, Sep 18, 2015 at 4:43 PM, Jan Lehnardt wrote: > Great stuff, thanks! :) > > Jan > -- > >> On 18 Sep 2015, at 10:37, Robert Kowalski wrote: >> >> Hi! >> >> Update for all: I tested a

Re: Let's cut a Nano release

Hi! Update for all: I tested a transfer of a test repo together with Daniel, who is part of the ASF infra team to github.com/apache. The way of the repo was: robertkowalski -> Humbedooh -> apache The redirects still work with a "hop" in between over an ASF-root-person. I guess the last thing

Re: Let's cut a Nano release

Great stuff, thanks! :) Jan -- > On 18 Sep 2015, at 10:37, Robert Kowalski wrote: > > Hi! > > Update for all: I tested a transfer of a test repo together with Daniel, > who is part of the ASF infra team to github.com/apache. The way of the repo > was: > > robertkowalski ->

Re: Let's cut a Nano release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thats good news, thanks! On 18.09.2015 10:37, Robert Kowalski wrote: > Hi! > > Update for all: I tested a transfer of a test repo together with > Daniel, who is part of the ASF infra team to github.com/apache. The > way of the repo was: > >

Re: Let's cut a Nano release

Guys, to make sure are you waiting on any action on my behalf? Happy to do whatever apache seems fit, a single official email from apache and I’ll get it done, Take care, Nuno — Sent from Mailbox On Fri, Sep 4, 2015 at 1:26 AM, Robert Kowalski wrote: > Somehow I

Re: Let's cut a Nano release

Hi Nuno, thanks for offering your help! I don't think we wait for something from you, we are just trying to somehow get the repo transferred to the ASF so we can retain the issues. One thing we have to get working on the ASF side for it is to enable GitHub issues for the repo which are disabled

Re: Let's cut a Nano release

Somehow I got no answer on the ML - I opened a Jira ticket: https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10252 On Mon, Aug 17, 2015 at 4:26 PM, Johannes Jörg Schmidt wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, > > I am in

Re: Let's cut a Nano release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I am in favor of a repo transfer because - - the redirect - - issues and issue history - - pull requests (there are two currently open where I do not have any opinion, sorry!) - - startgazers - - wiki If that would be possible in any way

Let's cut a Nano release

Hi, dev@. And hi, Johannes (hope you see this). Last month, you asked what to do about releasing Apache Nano (or Apache CouchDB Nano, or whatever its name is). I would like to get involved in that effort, and to help push it forward. Nuno and the team graciously donated the project to the ASF.

Re: Let's cut a Nano release

Hey Jason, thanks for bringing this up again! Really appreciated! 1. cool! 2. For Fauxton we just use the Component field in Jira. Do you mean setting up a whole new Jira (e.g. CouchDB, Cassandra) or setting up a subcomponent. The latter is easy, just type in the new component name when

Re: Let's cut a Nano release

On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski r...@kowalski.gd wrote: 3. Can you chime in at [1] ? Can you open the link? I basically asked infra if we can have Github issues enabled in all our subprojects and if they can migrate nano for us together with issues, wiki, closed/open/prs etc.

Re: Let's cut a Nano release

Yes On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin kxe...@gmail.com wrote: On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski r...@kowalski.gd wrote: 3. Can you chime in at [1] ? Can you open the link? I basically asked infra if we can have Github issues enabled in all our subprojects

Re: Let's cut a Nano release

i think infra could just accept the repo once there is a possibility in having github issues for asf projects i have transferred a lot of repos (but not with the asf). the cool thing is that you get a redirect for free, keep all your previous issues, wikis, PRs etc... On Wed, Aug 12, 2015 at

Re: Let's cut a Nano release

Right, good point, Alexander. In that case, I would say, let's not do an actual GitHub transfer. There are only a few tickets. I think we could move the key ones over by hand ourselves; and in the fullness of time, it won't much matter. On Wed, Aug 12, 2015 at 2:39 AM, Robert Kowalski