Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369704

Summary: LTS Bugzilla
Product: Working Groups Reporter: Andrea Ross <andrea.ross>
Component: LTSAssignee: LTS Infrastructure Inbox <lts.infrastructure-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: andrea.ross, denis.roy, sbouchet
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on: 369707    
Bug Blocks:    

Description Andrea Ross CLA 2012-01-25 11:56:30 EST 
This ticket is for tracking discussion and work related to hosting Bugzilla use in the Long Term Support (LTS) forge. Bugzilla will be shared between the Community forge and LTS forge. Meta data will be used to route bugs appropriately.
Comment 1 Andrea Ross CLA 2012-01-31 10:44:22 EST 
We'll need a mechanism such as cloning bugs to track them being propped into various LTS branches. This process also facilitates the change control board's decision process.

Each bug should be linked to the original bug for traceability purposes. Thus we need meta data to track each LTS version/release of each software unit/project.

Which is original? The options are:
1) The fix in the latest and greatest community code [recommended]
2) The fix in the first release it was detected.

The advantages to #1:
a) Less risk of a fix disappearing when people update their software because of a neglected prop.
b) A chance the issue was already fixed.
c) Consistency in that there's always one place to go first.
d) Chance control processes have one place to look for input as to which fixes need a decision whether to prop or not.

The advantages to #2:
a) Quicker turn around to a fix being available in the field deployed version of the software.
Comment 2 Denis Roy CLA 2014-05-27 09:01:37 EDT 
Moving to the Working Groups section.
Comment 3 Denis Roy CLA 2020-04-13 14:20:31 EDT 
LTS is no longer active.