You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Konstantin Boudnik <co...@apache.org> on 2015/01/02 19:27:53 UTC
Fwd: [jira] [Commented] (INFRA-8820) Create CMS for Apache Ignite
(incubating)
Fellas,
do we want to change current svnpub website publishing to CMS one? I believe
the current method works well, as it doesn't need any extra steps once the
content is commit. Please chime in on the ticket if you want a change -
otherwise it will get closed automatically.
Cos
----- Forwarded message from "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> -----
Date: Fri, 2 Jan 2015 13:21:14 +0000 (UTC)
From: "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>
To: cos@apache.org
Subject: [jira] [Commented] (INFRA-8820) Create CMS for Apache Ignite (incubating)
[ https://issues.apache.org/jira/browse/INFRA-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262892#comment-14262892 ]
#asfinfra IRC Bot commented on INFRA-8820:
------------------------------------------
This issue is being automatically transitioned to 'Pending Closed' because it has been waiting for user feedback for at least 3 days.
The issue will be automatically closed in 7 days if not further action is taken.
To prevent the issue from being closed all you need to do is update the issue.
> Create CMS for Apache Ignite (incubating)
> -----------------------------------------
>
> Key: INFRA-8820
> URL: https://issues.apache.org/jira/browse/INFRA-8820
> Project: Infrastructure
> Issue Type: Task
> Components: CMS
> Reporter: Roman Shaposhnik
> Assignee: Geoffrey Corey
>
> Please provide CMS capability for Apache Ignite (incubating)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
----- End forwarded message -----
Re: Fwd: [jira] [Commented] (INFRA-8820) Create CMS for Apache
Ignite (incubating)
Posted by Konstantin Boudnik <co...@apache.org>.
My sentiment exactly. I will comment on the ticket and close it.
Thanks,
Cos
On Fri, Jan 02, 2015 at 04:31PM, Dmitriy Setrakyan wrote:
> Thanks Brane,
>
> I agree. I don't think we need a CMS at this point. Plain PubSub is good
> enough for us at this point.
>
> D.
>
> On Fri, Jan 2, 2015 at 2:15 PM, Branko Čibej <br...@apache.org> wrote:
>
> > On 02.01.2015 19:27, Konstantin Boudnik wrote:
> > > Fellas,
> > >
> > > do we want to change current svnpub website publishing to CMS one? I
> > believe
> > > the current method works well, as it doesn't need any extra steps once
> > the
> > > content is commit. Please chime in on the ticket if you want a change -
> > > otherwise it will get closed automatically.
> >
> > My personal opinion is that our homegrown CMS spontaneously creates a
> > sustained region of high-grade vacuum.[1] If PubSub is good enough, I
> > suggest to keep that and not complicate matters.
> >
> > -- Brane
> >
> > [1] Translation: it sucks.
> >
> >
Re: Fwd: [jira] [Commented] (INFRA-8820) Create CMS for Apache Ignite (incubating)
Posted by Dmitriy Setrakyan <ds...@gridgain.com>.
Thanks Brane,
I agree. I don't think we need a CMS at this point. Plain PubSub is good
enough for us at this point.
D.
On Fri, Jan 2, 2015 at 2:15 PM, Branko Čibej <br...@apache.org> wrote:
> On 02.01.2015 19:27, Konstantin Boudnik wrote:
> > Fellas,
> >
> > do we want to change current svnpub website publishing to CMS one? I
> believe
> > the current method works well, as it doesn't need any extra steps once
> the
> > content is commit. Please chime in on the ticket if you want a change -
> > otherwise it will get closed automatically.
>
> My personal opinion is that our homegrown CMS spontaneously creates a
> sustained region of high-grade vacuum.[1] If PubSub is good enough, I
> suggest to keep that and not complicate matters.
>
> -- Brane
>
> [1] Translation: it sucks.
>
>
Re: Fwd: [jira] [Commented] (INFRA-8820) Create CMS for Apache Ignite
(incubating)
Posted by Branko Čibej <br...@apache.org>.
On 02.01.2015 19:27, Konstantin Boudnik wrote:
> Fellas,
>
> do we want to change current svnpub website publishing to CMS one? I believe
> the current method works well, as it doesn't need any extra steps once the
> content is commit. Please chime in on the ticket if you want a change -
> otherwise it will get closed automatically.
My personal opinion is that our homegrown CMS spontaneously creates a
sustained region of high-grade vacuum.[1] If PubSub is good enough, I
suggest to keep that and not complicate matters.
-- Brane
[1] Translation: it sucks.