Bug 837555

Summary:	RFE: clients to show server version as well as API version
Product:	[Retired] Zanata	Reporter:	Parag Nemade <pnemade>
Component:	Component-PythonClient, Component-Logic, Component-Maven	Assignee:	Runa Bhattacharjee <runab>
Status:	CLOSED WONTFIX	QA Contact:	Ding-Yi Chen <dchen>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	ankit, damason, sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-21 03:00:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Parag Nemade 2012-07-04 08:50:27 UTC

Description of problem:
I see zanata server deployed is 1.6.1 version whereas zanata push/pull shows
zanata python client version: 1.3.7, zanata server API version: 1.6.0

Why is there  difference in zanata server version?


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 David Mason 2012-07-05 03:05:25 UTC

The server version and API version can change independently. Version 1.6.1 of the server uses version 1.6.0 of the client.

I recommend showing both server and API versions in the output to make it clear that these are two different things.

e.g. the output above would be changed to:-
zanata python client version: 1.3.7, zanata server version: 1.6.1, zanata API version: 1.6.0

Comment 2 David Mason 2012-07-05 03:07:06 UTC

First paragraph above should end "version 1.6.0 of the API"

Comment 3 Parag Nemade 2012-08-06 13:57:30 UTC

What is a need to select 3 different components for this bug?

Comment 4 Parag Nemade 2012-08-09 15:12:54 UTC

Can some one please review why this bug is against 3 components? This un-necessarily making component field fatter, thus my bug tracker list becomes last field summary hyphenated.

Comment 5 Parag Nemade 2012-08-09 15:20:37 UTC

and date field is completely invisible and I need to use horizontal scroll :-(

Comment 6 Sean Flanigan 2012-08-09 23:40:37 UTC

It's on three components because work will be required on both clients and on the server.

Why do you consider this RFE to be urgent?

Comment 7 Parag Nemade 2012-08-10 03:52:16 UTC

I have already explained what problem I am facing. This is not at all urgent to me. Urgency is because someone to check this and select a correct single component. 

Wish I was not the owner of this bug. I would have removed myself immediately as its causing visibility issue for my bug tracker.

Anyway I have been forcefully rearranged my bug tracker fields.

resetting severity and priority.

Comment 8 Parag Nemade 2012-09-19 07:47:07 UTC

Any progress on this ***three component*** bug?

Comment 9 Sean Flanigan 2012-09-21 03:00:52 UTC

This feature isn't planned on the roadmap.

Comment 10 Parag Nemade 2012-09-21 03:03:16 UTC

Thanks for closing this. Lets hope the confusion continues for the end user.