JIRA and Infrastructure (was Re: Managing API review requests)

[Daniel Zwolenski]

+1 on fixing JIRA and using all the Confluence tools better. Seems counter
productive to have the best tools on the market and then use them in a very
clunky way.

I know this is an Oracle infrastructure issue and so in the bowels of
politics, red tape and bureaucracy. I suppose I'd be being completely
idealistically unrealistic to think you could move it all over to
Atlassian's hosted solution:
http://www.atlassian.com/software/ondemand/and cut out the Oracle
Big-Corporate black hole; latest versions, all
integrated, all managed, all nice. I'm sure the Atlassian guys would work
out a deal of some kind.

Had to suggest it out, but, yea, I know, I'm dreaming.



On Sat, Jan 19, 2013 at 5:45 AM, Mark Fortner <phidias51 at gmail.com> wrote:

> When things get a little clearer, could you guys add target version numbers
> to those?  It would make it little easier for the rest of us.  This could
> be done by simply appending the version number to the name in JIRA (i.e.
> "Van Ness - 9.0"). I can usually figure out that 1.8 release happens after
> a 1.7 release, but code names don't really tell me much. :-)
>
> Cheers,
>
> Mark
>
>
>
> On Fri, Jan 18, 2013 at 10:31 AM, Kevin Rushforth <
> kevin.rushforth at oracle.com> wrote:
>
> > **
> >
> > Hahaha :-). I just learned this one yesterday, that is the next release
> after Lombard. What I don't know is if that is the next update release or
> the next major release, Kevin will have to fill us in :-)
> >
> >
> > I just heard of "Van Ness" the day before yesterday. :)
> >
> > It is intended to be the next major release, which would line up with
> > JDK9, but I expect there might be some further clarification needed.
> > (how's that for a non-answer answer?)
> >
> > -- Kevin
> >
> >
> >
> >
> > Richard Bair wrote:
> >
> >  If it would help for me or others to provide feedback to them to
> perhaps spur them on, let me know.
> >
> >
> >  Thanks :-).
> >
> >
> >
> >  There are other issues with the current JIRA configuration that I'd
> like them to address that would also make things easier like SSO
> >
> >
> >  Yes, we're working on an SSO solution as well. Basically we're trying
> to use a full suite of Atlassian tools and have a SSO for all of them, and
> I believe it is all tied into Oracle SSO, but I am shady on the details.
> >
> >
> >
> >  screen capture applet misconfiguration
> >
> >
> >  I haven't tried it, what is the problem? At some point when OpenJDK
> opens up their JIRA instance we'll start a migration effort to move to it,
> so if there is some misconfiguration we can test on the new instance and
> see if it is still problem there.
> >
> >
> >
> >  and the ever pesky "what the hell is the 'Van Ness' release" question.
> :-)
> >
> >
> >  Hahaha :-). I just learned this one yesterday, that is the next release
> after Lombard. What I don't know is if that is the next update release or
> the next major release, Kevin will have to fill us in :-)
> >
> > Richard
> >
> >
>