Bug 283862 - [Metadata] Consider switching from CVS modules to PSFs
Summary: [Metadata] Consider switching from CVS modules to PSFs
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-17 11:14 EDT by Paul Webster CLA
Modified: 2019-09-06 15:30 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Webster CLA 2009-07-17 11:14:46 EDT 
we usually have a hard time keeping our CVS modules up to date.  As well, they're not branched (it's always a problem trying to load up a maintenance release that doesn't include new plugins).

We should consider creating 3 PSFs instead, so we can:
1) branch them
2) update the PSFs in maintenance branches so that they actually check out the correct projects already tagged or in the branch

We can transition in 3.6 and then back-port the PSFs to 3.5, 3.4, and I would also try 3.3


PW
Comment 1 Boris Bokowski CLA 2009-07-17 14:50:04 EDT 
+1 (ideally, we would get the CVS guys to support "import psf" based off of a psf file in the repository, without having to check anything out first).
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:30:19 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.