You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Jason Smith <ja...@gmail.com> on 2015/08/11 08:13:47 UTC
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. I know that
much. Here are some open questions I feel remain.
1. There are still commits going into github.com/dscape/nano although only
Johannes so-far. I will submit a pull request to dscape to update the
README to point to the ASF project.
2. We have no JIRA project for it. May I get involved in creating that? Any
tips?
3. We have no issue tracker in GitHub either. For me, I would personally do
what I once learned from Jan ("collect feedback from customers where they
are"). So I would like to have github issues if possible? Any way I can
help?
4. What about publishing to npm? IMO, le mieux, c'est l'ennemi du bien, I
am happy asking Johannes to prepare a Git tag, then ask Johannes to `git
pull; git checkout; npm publish`. And then we can sort out the "real" fix
later, yeah?
5. What about publishing outside of npm? Must we still cut the release
artifacts, and have the VOTEs? My feeling is, the vote is proper and
useful, but the release artifacts are largely useless, given the ubiquity
of npm in the Node.js community.
Thanks, all!
Re: Let's cut a Nano release
Posted by Nuno Job <nu...@gmail.com>.
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 <ga...@apache.org> wrote:
> 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 plans to do more development on it to bring it up to date with CouchDB
> 2.0 which is awesome news. How do we push a release and can we update the
> package.json to point to the couchdb-nano one?
>
> Cheers
> Garren
>
> On Sat, Dec 12, 2015 at 3:04 PM, Jan Lehnardt <ja...@apache.org> wrote:
>
> > Does this stop us from cutting a release?
> >
> > Best
> > Jan
> > --
> >
> > > On 06 Dec 2015, at 23:50, Robert Kowalski <ro...@kowalski.gd> 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 <ja...@apache.org> wrote:
> > >> Great stuff, thanks! :)
> > >>
> > >> Jan
> > >> --
> > >>
> > >>> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
> > >>>
> > >>> The redirects still work with a "hop" in between over an
> > ASF-root-person.
> > >>>
> > >>> I guess the last thing we need now to happen is that GitHub ships the
> > new
> > >>> permissions API that they have announced recently.
> > >>>
> > >>> It is a small success on our way, but also a big one because it
> proves
> > that
> > >>> our idea works :)
> > >>>
> > >>> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd>
> > wrote:
> > >>>
> > >>>> 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 by default. I
> > >>>> know Infra at least plans to support GitHub issues once GitHub
> > >>>> released their new permissions API.
> > >>>>
> > >>>> Once we figured out the nitty gritty details with infra we'll ping
> > >>>> you, but until then don't worry! :)
> > >>>>
> > >>>>
> > >>>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com>
> > wrote:
> > >>>>> 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 <ro...@kowalski.gd>
> > wrote:
> > >>>>>
> > >>>>>> 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
> > >>>>>> <sc...@netzmerk.com> wrote:
> > >>>>>>> -----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 it would be awesome.
> > >>>>>>>
> > >>>>>>> :) Johannes
> > >>>>>>>
> > >>>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
> > >>>>>>>> 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 3:34 AM, Jason Smith
> > >>>>>>>> <ja...@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>>> 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
> > >>>>>>>>> <ro...@kowalski.gd> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> Yes
> > >>>>>>>>>>
> > >>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
> > >>>>>>>>>> <kx...@gmail.com> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
> > >>>>>>>>>>> <ro...@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.
> > >>>>>>>>> If
> > >>>>>>>>>>> you
> > >>>>>>>>>>>> can not open the link, please ping me!
> > >>>>>>>>>>>
> > >>>>>>>>>>> That's only possible if you'll transfer original GH nano
> > >>>>>>>>>>> repository to Apache GH account. This also means that current
> > >>>>>>>>>>> couchdb-nano have to be removed.
> > >>>>>>>>>>>
> > >>>>>>>>>>> -- ,,,^..^,,,
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>> -----BEGIN PGP SIGNATURE-----
> > >>>>>>> Version: GnuPG v2
> > >>>>>>>
> > >>>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
> > >>>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
> > >>>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
> > >>>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
> > >>>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
> > >>>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
> > >>>>>>> =WWJd
> > >>>>>>> -----END PGP SIGNATURE-----
> > >>>>
> > >>
> > >> --
> > >> Professional Support for Apache CouchDB:
> > >> http://www.neighbourhood.ie/couchdb-support/
> > >>
> >
> >
>
Re: Let's cut a Nano release
Posted by Glynn Bird <gl...@gmail.com>.
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 could show a 'deprecated' warning and link to
apache/couchdb-nano
My PR updates the project's dependencies which were somewhat stale, brings
over the commits from the dscape/nano project that were not in
apache/couchdb-nano, updates the test suite and Travis config to test
against CouchDB 2.0.
I have other minor fixes to do, but I wanted to get the dust blown of the
project first.
Glynn
On Thu, 27 Oct 2016 at 10:56 Garren Smith <ga...@apache.org> wrote:
> 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 plans to do more development on it to bring it up to date with CouchDB
> 2.0 which is awesome news. How do we push a release and can we update the
> package.json to point to the couchdb-nano one?
>
> Cheers
> Garren
>
> On Sat, Dec 12, 2015 at 3:04 PM, Jan Lehnardt <ja...@apache.org> wrote:
>
> > Does this stop us from cutting a release?
> >
> > Best
> > Jan
> > --
> >
> > > On 06 Dec 2015, at 23:50, Robert Kowalski <ro...@kowalski.gd> 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 <ja...@apache.org> wrote:
> > >> Great stuff, thanks! :)
> > >>
> > >> Jan
> > >> --
> > >>
> > >>> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
> > >>>
> > >>> The redirects still work with a "hop" in between over an
> > ASF-root-person.
> > >>>
> > >>> I guess the last thing we need now to happen is that GitHub ships the
> > new
> > >>> permissions API that they have announced recently.
> > >>>
> > >>> It is a small success on our way, but also a big one because it
> proves
> > that
> > >>> our idea works :)
> > >>>
> > >>> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd>
> > wrote:
> > >>>
> > >>>> 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 by default. I
> > >>>> know Infra at least plans to support GitHub issues once GitHub
> > >>>> released their new permissions API.
> > >>>>
> > >>>> Once we figured out the nitty gritty details with infra we'll ping
> > >>>> you, but until then don't worry! :)
> > >>>>
> > >>>>
> > >>>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com>
> > wrote:
> > >>>>> 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 <ro...@kowalski.gd>
> > wrote:
> > >>>>>
> > >>>>>> 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
> > >>>>>> <sc...@netzmerk.com> wrote:
> > >>>>>>> -----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 it would be awesome.
> > >>>>>>>
> > >>>>>>> :) Johannes
> > >>>>>>>
> > >>>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
> > >>>>>>>> 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 3:34 AM, Jason Smith
> > >>>>>>>> <ja...@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>>> 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
> > >>>>>>>>> <ro...@kowalski.gd> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> Yes
> > >>>>>>>>>>
> > >>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
> > >>>>>>>>>> <kx...@gmail.com> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
> > >>>>>>>>>>> <ro...@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.
> > >>>>>>>>> If
> > >>>>>>>>>>> you
> > >>>>>>>>>>>> can not open the link, please ping me!
> > >>>>>>>>>>>
> > >>>>>>>>>>> That's only possible if you'll transfer original GH nano
> > >>>>>>>>>>> repository to Apache GH account. This also means that current
> > >>>>>>>>>>> couchdb-nano have to be removed.
> > >>>>>>>>>>>
> > >>>>>>>>>>> -- ,,,^..^,,,
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>> -----BEGIN PGP SIGNATURE-----
> > >>>>>>> Version: GnuPG v2
> > >>>>>>>
> > >>>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
> > >>>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
> > >>>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
> > >>>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
> > >>>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
> > >>>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
> > >>>>>>> =WWJd
> > >>>>>>> -----END PGP SIGNATURE-----
> > >>>>
> > >>
> > >> --
> > >> Professional Support for Apache CouchDB:
> > >> http://www.neighbourhood.ie/couchdb-support/
> > >>
> >
> >
>
Re: Let's cut a Nano release
Posted by Garren Smith <ga...@apache.org>.
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 plans to do more development on it to bring it up to date with CouchDB
2.0 which is awesome news. How do we push a release and can we update the
package.json to point to the couchdb-nano one?
Cheers
Garren
On Sat, Dec 12, 2015 at 3:04 PM, Jan Lehnardt <ja...@apache.org> wrote:
> Does this stop us from cutting a release?
>
> Best
> Jan
> --
>
> > On 06 Dec 2015, at 23:50, Robert Kowalski <ro...@kowalski.gd> 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 <ja...@apache.org> wrote:
> >> Great stuff, thanks! :)
> >>
> >> Jan
> >> --
> >>
> >>> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
> >>>
> >>> The redirects still work with a "hop" in between over an
> ASF-root-person.
> >>>
> >>> I guess the last thing we need now to happen is that GitHub ships the
> new
> >>> permissions API that they have announced recently.
> >>>
> >>> It is a small success on our way, but also a big one because it proves
> that
> >>> our idea works :)
> >>>
> >>> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >>>
> >>>> 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 by default. I
> >>>> know Infra at least plans to support GitHub issues once GitHub
> >>>> released their new permissions API.
> >>>>
> >>>> Once we figured out the nitty gritty details with infra we'll ping
> >>>> you, but until then don't worry! :)
> >>>>
> >>>>
> >>>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com>
> wrote:
> >>>>> 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 <ro...@kowalski.gd>
> wrote:
> >>>>>
> >>>>>> 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
> >>>>>> <sc...@netzmerk.com> wrote:
> >>>>>>> -----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 it would be awesome.
> >>>>>>>
> >>>>>>> :) Johannes
> >>>>>>>
> >>>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
> >>>>>>>> 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 3:34 AM, Jason Smith
> >>>>>>>> <ja...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>>> 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
> >>>>>>>>> <ro...@kowalski.gd> wrote:
> >>>>>>>>>
> >>>>>>>>>> Yes
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
> >>>>>>>>>> <kx...@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
> >>>>>>>>>>> <ro...@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.
> >>>>>>>>> If
> >>>>>>>>>>> you
> >>>>>>>>>>>> can not open the link, please ping me!
> >>>>>>>>>>>
> >>>>>>>>>>> That's only possible if you'll transfer original GH nano
> >>>>>>>>>>> repository to Apache GH account. This also means that current
> >>>>>>>>>>> couchdb-nano have to be removed.
> >>>>>>>>>>>
> >>>>>>>>>>> -- ,,,^..^,,,
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> -----BEGIN PGP SIGNATURE-----
> >>>>>>> Version: GnuPG v2
> >>>>>>>
> >>>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
> >>>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
> >>>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
> >>>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
> >>>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
> >>>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
> >>>>>>> =WWJd
> >>>>>>> -----END PGP SIGNATURE-----
> >>>>
> >>
> >> --
> >> Professional Support for Apache CouchDB:
> >> http://www.neighbourhood.ie/couchdb-support/
> >>
>
>
Re: Let's cut a Nano release
Posted by Jan Lehnardt <ja...@apache.org>.
Does this stop us from cutting a release?
Best
Jan
--
> On 06 Dec 2015, at 23:50, Robert Kowalski <ro...@kowalski.gd> 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 <ja...@apache.org> wrote:
>> Great stuff, thanks! :)
>>
>> Jan
>> --
>>
>>> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
>>>
>>> The redirects still work with a "hop" in between over an ASF-root-person.
>>>
>>> I guess the last thing we need now to happen is that GitHub ships the new
>>> permissions API that they have announced recently.
>>>
>>> It is a small success on our way, but also a big one because it proves that
>>> our idea works :)
>>>
>>> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>>
>>>> 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 by default. I
>>>> know Infra at least plans to support GitHub issues once GitHub
>>>> released their new permissions API.
>>>>
>>>> Once we figured out the nitty gritty details with infra we'll ping
>>>> you, but until then don't worry! :)
>>>>
>>>>
>>>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com> wrote:
>>>>> 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 <ro...@kowalski.gd> wrote:
>>>>>
>>>>>> 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
>>>>>> <sc...@netzmerk.com> wrote:
>>>>>>> -----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 it would be awesome.
>>>>>>>
>>>>>>> :) Johannes
>>>>>>>
>>>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
>>>>>>>> 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 3:34 AM, Jason Smith
>>>>>>>> <ja...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>> <ro...@kowalski.gd> wrote:
>>>>>>>>>
>>>>>>>>>> Yes
>>>>>>>>>>
>>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>>>>>>> <kx...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>>>>>>> <ro...@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.
>>>>>>>>> If
>>>>>>>>>>> you
>>>>>>>>>>>> can not open the link, please ping me!
>>>>>>>>>>>
>>>>>>>>>>> That's only possible if you'll transfer original GH nano
>>>>>>>>>>> repository to Apache GH account. This also means that current
>>>>>>>>>>> couchdb-nano have to be removed.
>>>>>>>>>>>
>>>>>>>>>>> -- ,,,^..^,,,
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> -----BEGIN PGP SIGNATURE-----
>>>>>>> Version: GnuPG v2
>>>>>>>
>>>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
>>>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
>>>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
>>>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
>>>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
>>>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
>>>>>>> =WWJd
>>>>>>> -----END PGP SIGNATURE-----
>>>>
>>
>> --
>> Professional Support for Apache CouchDB:
>> http://www.neighbourhood.ie/couchdb-support/
>>
Re: Let's cut a Nano release
Posted by Alexander Shorin <kx...@gmail.com>.
Few months is still better than never. So it's good news (:
--
,,,^..^,,,
On Mon, Dec 7, 2015 at 1:50 AM, Robert Kowalski <ro...@kowalski.gd> 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 <ja...@apache.org> wrote:
>> Great stuff, thanks! :)
>>
>> Jan
>> --
>>
>>> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
>>>
>>> The redirects still work with a "hop" in between over an ASF-root-person.
>>>
>>> I guess the last thing we need now to happen is that GitHub ships the new
>>> permissions API that they have announced recently.
>>>
>>> It is a small success on our way, but also a big one because it proves that
>>> our idea works :)
>>>
>>> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>>
>>>> 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 by default. I
>>>> know Infra at least plans to support GitHub issues once GitHub
>>>> released their new permissions API.
>>>>
>>>> Once we figured out the nitty gritty details with infra we'll ping
>>>> you, but until then don't worry! :)
>>>>
>>>>
>>>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com> wrote:
>>>>> 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 <ro...@kowalski.gd> wrote:
>>>>>
>>>>>> 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
>>>>>> <sc...@netzmerk.com> wrote:
>>>>>>> -----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 it would be awesome.
>>>>>>>
>>>>>>> :) Johannes
>>>>>>>
>>>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
>>>>>>>> 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 3:34 AM, Jason Smith
>>>>>>>> <ja...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>> <ro...@kowalski.gd> wrote:
>>>>>>>>>
>>>>>>>>>> Yes
>>>>>>>>>>
>>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>>>>>>> <kx...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>>>>>>> <ro...@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.
>>>>>>>>> If
>>>>>>>>>>> you
>>>>>>>>>>>> can not open the link, please ping me!
>>>>>>>>>>>
>>>>>>>>>>> That's only possible if you'll transfer original GH nano
>>>>>>>>>>> repository to Apache GH account. This also means that current
>>>>>>>>>>> couchdb-nano have to be removed.
>>>>>>>>>>>
>>>>>>>>>>> -- ,,,^..^,,,
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> -----BEGIN PGP SIGNATURE-----
>>>>>>> Version: GnuPG v2
>>>>>>>
>>>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
>>>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
>>>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
>>>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
>>>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
>>>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
>>>>>>> =WWJd
>>>>>>> -----END PGP SIGNATURE-----
>>>>
>>
>> --
>> Professional Support for Apache CouchDB:
>> http://www.neighbourhood.ie/couchdb-support/
>>
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
Hi I got sad news:
https://issues.apache.org/jira/browse/INFRA-10252
On Fri, Sep 18, 2015 at 4:43 PM, Jan Lehnardt <ja...@apache.org> wrote:
> Great stuff, thanks! :)
>
> Jan
> --
>
>> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
>>
>> The redirects still work with a "hop" in between over an ASF-root-person.
>>
>> I guess the last thing we need now to happen is that GitHub ships the new
>> permissions API that they have announced recently.
>>
>> It is a small success on our way, but also a big one because it proves that
>> our idea works :)
>>
>> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>
>>> 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 by default. I
>>> know Infra at least plans to support GitHub issues once GitHub
>>> released their new permissions API.
>>>
>>> Once we figured out the nitty gritty details with infra we'll ping
>>> you, but until then don't worry! :)
>>>
>>>
>>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com> wrote:
>>>> 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 <ro...@kowalski.gd> wrote:
>>>>
>>>>> 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
>>>>> <sc...@netzmerk.com> wrote:
>>>>>> -----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 it would be awesome.
>>>>>>
>>>>>> :) Johannes
>>>>>>
>>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
>>>>>>> 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 3:34 AM, Jason Smith
>>>>>>> <ja...@gmail.com> wrote:
>>>>>>>
>>>>>>>> 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
>>>>>>>> <ro...@kowalski.gd> wrote:
>>>>>>>>
>>>>>>>>> Yes
>>>>>>>>>
>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>>>>>> <kx...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>>>>>> <ro...@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.
>>>>>>>> If
>>>>>>>>>> you
>>>>>>>>>>> can not open the link, please ping me!
>>>>>>>>>>
>>>>>>>>>> That's only possible if you'll transfer original GH nano
>>>>>>>>>> repository to Apache GH account. This also means that current
>>>>>>>>>> couchdb-nano have to be removed.
>>>>>>>>>>
>>>>>>>>>> -- ,,,^..^,,,
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> -----BEGIN PGP SIGNATURE-----
>>>>>> Version: GnuPG v2
>>>>>>
>>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
>>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
>>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
>>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
>>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
>>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
>>>>>> =WWJd
>>>>>> -----END PGP SIGNATURE-----
>>>
>
> --
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>
Re: Let's cut a Nano release
Posted by Jan Lehnardt <ja...@apache.org>.
Great stuff, thanks! :)
Jan
--
> On 18 Sep 2015, at 10:37, Robert Kowalski <ro...@kowalski.gd> 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 -> Humbedooh -> apache
>
> The redirects still work with a "hop" in between over an ASF-root-person.
>
> I guess the last thing we need now to happen is that GitHub ships the new
> permissions API that they have announced recently.
>
> It is a small success on our way, but also a big one because it proves that
> our idea works :)
>
> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> 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 by default. I
>> know Infra at least plans to support GitHub issues once GitHub
>> released their new permissions API.
>>
>> Once we figured out the nitty gritty details with infra we'll ping
>> you, but until then don't worry! :)
>>
>>
>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com> wrote:
>>> 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 <ro...@kowalski.gd> wrote:
>>>
>>>> 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
>>>> <sc...@netzmerk.com> wrote:
>>>>> -----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 it would be awesome.
>>>>>
>>>>> :) Johannes
>>>>>
>>>>> On 12.08.2015 03:38, Robert Kowalski wrote:
>>>>>> 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 3:34 AM, Jason Smith
>>>>>> <ja...@gmail.com> wrote:
>>>>>>
>>>>>>> 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
>>>>>>> <ro...@kowalski.gd> wrote:
>>>>>>>
>>>>>>>> Yes
>>>>>>>>
>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>>>>> <kx...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>>>>> <ro...@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.
>>>>>>> If
>>>>>>>>> you
>>>>>>>>>> can not open the link, please ping me!
>>>>>>>>>
>>>>>>>>> That's only possible if you'll transfer original GH nano
>>>>>>>>> repository to Apache GH account. This also means that current
>>>>>>>>> couchdb-nano have to be removed.
>>>>>>>>>
>>>>>>>>> -- ,,,^..^,,,
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> -----BEGIN PGP SIGNATURE-----
>>>>> Version: GnuPG v2
>>>>>
>>>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
>>>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
>>>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
>>>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
>>>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
>>>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
>>>>> =WWJd
>>>>> -----END PGP SIGNATURE-----
>>
--
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/
Re: Let's cut a Nano release
Posted by Johannes Jörg Schmidt <sc...@netzmerk.com>.
-----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:
>
> robertkowalski -> Humbedooh -> apache
>
> The redirects still work with a "hop" in between over an
> ASF-root-person.
>
> I guess the last thing we need now to happen is that GitHub ships
> the new permissions API that they have announced recently.
>
> It is a small success on our way, but also a big one because it
> proves that our idea works :)
>
> On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
>
>> 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 by
>> default. I know Infra at least plans to support GitHub issues
>> once GitHub released their new permissions API.
>>
>> Once we figured out the nitty gritty details with infra we'll
>> ping you, but until then don't worry! :)
>>
>>
>> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com>
>> wrote:
>>> 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
>>> <ro...@kowalski.gd> wrote:
>>>
>>>> Somehow I got no answer on the ML - I opened a Jira ticket:
>>>>
>> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10
252
>>>>
>>
On Mon, Aug 17, 2015 at 4:26 PM, Johannes Jörg Schmidt
>>>> <sc...@netzmerk.com> wrote:
> 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 it would be awesome.
>
> :) Johannes
>
> On 12.08.2015 03:38, Robert Kowalski wrote:
>>>>>>> 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 3:34 AM, Jason Smith
>>>>>>> <ja...@gmail.com> wrote:
>>>>>>>
>>>>>>>> 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
>>>>>>>> <ro...@kowalski.gd> wrote:
>>>>>>>>
>>>>>>>>> Yes
>>>>>>>>>
>>>>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>>>>>> <kx...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>>>>>> <ro...@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.
>>>>>>>> If
>>>>>>>>>> you
>>>>>>>>>>> can not open the link, please ping me!
>>>>>>>>>>
>>>>>>>>>> That's only possible if you'll transfer original
>>>>>>>>>> GH nano repository to Apache GH account. This
>>>>>>>>>> also means that current couchdb-nano have to be
>>>>>>>>>> removed.
>>>>>>>>>>
>>>>>>>>>> -- ,,,^..^,,,
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJV/CJSAAoJED+W7gN+c0gchXUH/Rp7t5MD7szMK+dDqIqCUaWW
ee/lyLxgkNFGEhzCCdBxnQxHCdzUv3tZEEUxsdcToAxqjUYDs12oYOLRjyTRoegw
rj6OAzQYGAqb3w1fbCqrO9NKAw6W98HwoOfJ8MwNnRIvQJNc0lVJ7N93MhlisS/A
KgdSD82vjxiLY60jaIO4jXZCHIRDED5abQO1TatclzP01XpsXu/Siw3ZMKzBgrgF
Yygdb5MWSbdW+f5vaV/dWkMEbHYvew9cBH5C5hQvdTW+JmW/lFGPZCxb5g8EPOIE
sObT6qh/8+dFy5ZNufH3FcwTBGozNJtUuozfL4rCPaI0UUW71wS6ixwTInIILYU=
=W9yq
-----END PGP SIGNATURE-----
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
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 we need now to happen is that GitHub ships the new
permissions API that they have announced recently.
It is a small success on our way, but also a big one because it proves that
our idea works :)
On Fri, Sep 4, 2015 at 9:09 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
> 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 by default. I
> know Infra at least plans to support GitHub issues once GitHub
> released their new permissions API.
>
> Once we figured out the nitty gritty details with infra we'll ping
> you, but until then don't worry! :)
>
>
> On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com> wrote:
> > 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 <ro...@kowalski.gd> wrote:
> >
> >> 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
> >> <sc...@netzmerk.com> wrote:
> >>> -----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 it would be awesome.
> >>>
> >>> :) Johannes
> >>>
> >>> On 12.08.2015 03:38, Robert Kowalski wrote:
> >>>> 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 3:34 AM, Jason Smith
> >>>> <ja...@gmail.com> wrote:
> >>>>
> >>>>> 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
> >>>>> <ro...@kowalski.gd> wrote:
> >>>>>
> >>>>>> Yes
> >>>>>>
> >>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
> >>>>>> <kx...@gmail.com> wrote:
> >>>>>>
> >>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
> >>>>>>> <ro...@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.
> >>>>> If
> >>>>>>> you
> >>>>>>>> can not open the link, please ping me!
> >>>>>>>
> >>>>>>> That's only possible if you'll transfer original GH nano
> >>>>>>> repository to Apache GH account. This also means that current
> >>>>>>> couchdb-nano have to be removed.
> >>>>>>>
> >>>>>>> -- ,,,^..^,,,
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>> -----BEGIN PGP SIGNATURE-----
> >>> Version: GnuPG v2
> >>>
> >>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
> >>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
> >>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
> >>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
> >>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
> >>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
> >>> =WWJd
> >>> -----END PGP SIGNATURE-----
>
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
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 by default. I
know Infra at least plans to support GitHub issues once GitHub
released their new permissions API.
Once we figured out the nitty gritty details with infra we'll ping
you, but until then don't worry! :)
On Fri, Sep 4, 2015 at 3:47 PM, Nuno Job <nu...@gmail.com> wrote:
> 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 <ro...@kowalski.gd> wrote:
>
>> 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
>> <sc...@netzmerk.com> wrote:
>>> -----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 it would be awesome.
>>>
>>> :) Johannes
>>>
>>> On 12.08.2015 03:38, Robert Kowalski wrote:
>>>> 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 3:34 AM, Jason Smith
>>>> <ja...@gmail.com> wrote:
>>>>
>>>>> 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
>>>>> <ro...@kowalski.gd> wrote:
>>>>>
>>>>>> Yes
>>>>>>
>>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>>> <kx...@gmail.com> wrote:
>>>>>>
>>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>>> <ro...@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.
>>>>> If
>>>>>>> you
>>>>>>>> can not open the link, please ping me!
>>>>>>>
>>>>>>> That's only possible if you'll transfer original GH nano
>>>>>>> repository to Apache GH account. This also means that current
>>>>>>> couchdb-nano have to be removed.
>>>>>>>
>>>>>>> -- ,,,^..^,,,
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v2
>>>
>>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
>>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
>>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
>>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
>>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
>>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
>>> =WWJd
>>> -----END PGP SIGNATURE-----
Re: Let's cut a Nano release
Posted by Nuno Job <nu...@gmail.com>.
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 <ro...@kowalski.gd> wrote:
> 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
> <sc...@netzmerk.com> wrote:
>> -----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 it would be awesome.
>>
>> :) Johannes
>>
>> On 12.08.2015 03:38, Robert Kowalski wrote:
>>> 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 3:34 AM, Jason Smith
>>> <ja...@gmail.com> wrote:
>>>
>>>> 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
>>>> <ro...@kowalski.gd> wrote:
>>>>
>>>>> Yes
>>>>>
>>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>>> <kx...@gmail.com> wrote:
>>>>>
>>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>>> <ro...@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.
>>>> If
>>>>>> you
>>>>>>> can not open the link, please ping me!
>>>>>>
>>>>>> That's only possible if you'll transfer original GH nano
>>>>>> repository to Apache GH account. This also means that current
>>>>>> couchdb-nano have to be removed.
>>>>>>
>>>>>> -- ,,,^..^,,,
>>>>>>
>>>>>
>>>>
>>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2
>>
>> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
>> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
>> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
>> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
>> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
>> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
>> =WWJd
>> -----END PGP SIGNATURE-----
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
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
<sc...@netzmerk.com> wrote:
> -----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 it would be awesome.
>
> :) Johannes
>
> On 12.08.2015 03:38, Robert Kowalski wrote:
>> 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 3:34 AM, Jason Smith
>> <ja...@gmail.com> wrote:
>>
>>> 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
>>> <ro...@kowalski.gd> wrote:
>>>
>>>> Yes
>>>>
>>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>>> <kx...@gmail.com> wrote:
>>>>
>>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>>> <ro...@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.
>>> If
>>>>> you
>>>>>> can not open the link, please ping me!
>>>>>
>>>>> That's only possible if you'll transfer original GH nano
>>>>> repository to Apache GH account. This also means that current
>>>>> couchdb-nano have to be removed.
>>>>>
>>>>> -- ,,,^..^,,,
>>>>>
>>>>
>>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
> 1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
> bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
> lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
> pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
> T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
> =WWJd
> -----END PGP SIGNATURE-----
Re: Let's cut a Nano release
Posted by Johannes Jörg Schmidt <sc...@netzmerk.com>.
-----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 it would be awesome.
:) Johannes
On 12.08.2015 03:38, Robert Kowalski wrote:
> 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 3:34 AM, Jason Smith
> <ja...@gmail.com> wrote:
>
>> 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
>> <ro...@kowalski.gd> wrote:
>>
>>> Yes
>>>
>>> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin
>>> <kx...@gmail.com> wrote:
>>>
>>>> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski
>>>> <ro...@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.
>> If
>>>> you
>>>>> can not open the link, please ping me!
>>>>
>>>> That's only possible if you'll transfer original GH nano
>>>> repository to Apache GH account. This also means that current
>>>> couchdb-nano have to be removed.
>>>>
>>>> -- ,,,^..^,,,
>>>>
>>>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJV0e78AAoJED+W7gN+c0gcHLsH/2kii63zT8IWA/a90OS1WGKI
1mCic03mVeU6grm5C3lGpgx22Y+RyyPjB9VH6sCvqGwjeb5DeooLAp0iLsR2V8OZ
bML/Ptr3bUsf5LzmnEAnDKOTOlmQRCwQj3FOhWwmMjLPXK3zcZPqE0Xs1px3w/Mr
lyjy7nfQb53SuOq4u70C1BpllvDnwFrQntbxkVam9d4OD66Dh+J1cMNPWhidIZWr
pKWkv8np9cpf52DaFORSLyQd5i/mXpfIAL/CRA5DzYoKcCm/lEGkuZDr2a6cSbGy
T3KRLU4m3EMDCb7kuquLz1+gTe1+zpVXtpThobfCUdaTTtnidyd/zIclLBSZx1g=
=WWJd
-----END PGP SIGNATURE-----
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
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 3:34 AM, Jason Smith <ja...@gmail.com>
wrote:
> 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 <ro...@kowalski.gd> wrote:
>
> > Yes
> >
> > On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin <kx...@gmail.com>
> > wrote:
> >
> > > On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski <ro...@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.
> If
> > > you
> > > > can not open the link, please ping me!
> > >
> > > That's only possible if you'll transfer original GH nano repository to
> > > Apache GH account. This also means that current couchdb-nano have to
> > > be removed.
> > >
> > > --
> > > ,,,^..^,,,
> > >
> >
>
Re: Let's cut a Nano release
Posted by Jason Smith <ja...@gmail.com>.
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 <ro...@kowalski.gd> wrote:
> Yes
>
> On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin <kx...@gmail.com>
> wrote:
>
> > On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski <ro...@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. If
> > you
> > > can not open the link, please ping me!
> >
> > That's only possible if you'll transfer original GH nano repository to
> > Apache GH account. This also means that current couchdb-nano have to
> > be removed.
> >
> > --
> > ,,,^..^,,,
> >
>
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
Yes
On Tue, Aug 11, 2015 at 12:25 PM, Alexander Shorin <kx...@gmail.com> wrote:
> On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski <ro...@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. If
> you
> > can not open the link, please ping me!
>
> That's only possible if you'll transfer original GH nano repository to
> Apache GH account. This also means that current couchdb-nano have to
> be removed.
>
> --
> ,,,^..^,,,
>
Re: Let's cut a Nano release
Posted by Alexander Shorin <kx...@gmail.com>.
On Tue, Aug 11, 2015 at 1:21 PM, Robert Kowalski <ro...@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. If you
> can not open the link, please ping me!
That's only possible if you'll transfer original GH nano repository to
Apache GH account. This also means that current couchdb-nano have to
be removed.
--
,,,^..^,,,
Re: Let's cut a Nano release
Posted by Robert Kowalski <ro...@kowalski.gd>.
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
creating a ticket.
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. If you
can not open the link, please ping me!
5. Yes I think we still need votes for an official apache release. Yes, I
agree.
[1]
https://mail-search.apache.org/pmc/private-arch/infrastructure/201507.mbox/%3CCAJ1bcfG9isogmctdqOOHAr8EPv3DONGK+z=xBBORSjm6MV0qYg@mail.gmail.com%3E
On Tue, Aug 11, 2015 at 8:13 AM, Jason Smith <ja...@gmail.com>
wrote:
> 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. I know that
> much. Here are some open questions I feel remain.
>
> 1. There are still commits going into github.com/dscape/nano although only
> Johannes so-far. I will submit a pull request to dscape to update the
> README to point to the ASF project.
>
> 2. We have no JIRA project for it. May I get involved in creating that? Any
> tips?
>
> 3. We have no issue tracker in GitHub either. For me, I would personally do
> what I once learned from Jan ("collect feedback from customers where they
> are"). So I would like to have github issues if possible? Any way I can
> help?
>
> 4. What about publishing to npm? IMO, le mieux, c'est l'ennemi du bien, I
> am happy asking Johannes to prepare a Git tag, then ask Johannes to `git
> pull; git checkout; npm publish`. And then we can sort out the "real" fix
> later, yeah?
>
> 5. What about publishing outside of npm? Must we still cut the release
> artifacts, and have the VOTEs? My feeling is, the vote is proper and
> useful, but the release artifacts are largely useless, given the ubiquity
> of npm in the Node.js community.
>
> Thanks, all!
>