Bug 253271 - define convention for project's properties bits
Summary: define convention for project's properties bits
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Dash Athena (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Common Build Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation
Depends on: 253266
Blocks: 253279 253283
  Show dependency tree
 
Reported: 2008-11-03 14:53 EST by Andrew Overholt CLA
Modified: 2012-01-30 11:31 EST (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 Andrew Overholt CLA 2008-11-03 14:53:29 EST 
Option #1:

{root}/releng containing a model or properties file(s)

Option #2:

{project}.releng project containing properties file(s) or a model
Comment 1 Andrew Overholt CLA 2008-11-14 16:46:31 EST 
Perhaps .cbi instead of .releng?
Comment 2 Nick Boldt CLA 2008-11-15 00:33:01 EST 
This only matters in terms of what automated filesystem watchers will use to automatically run builds based on the "if file exists, do a build; if not, it's up to the project to manually run stuff".

I'd suggest we support both conventions.

> Perhaps .cbi instead of .releng?

If we're done with "releng" (since this is much simpler than the stuff from basebuilder's templates) then how about using an "athena" folder or suffix?
Comment 3 Nick Boldt CLA 2008-11-15 00:40:44 EST 
This blocks bug 253283 - Define opt-in/opt-out mechanism for projects
Comment 4 Nick Boldt CLA 2009-01-16 11:57:52 EST 
slip
Comment 5 Nick Boldt CLA 2009-07-29 02:38:20 EDT 
Personally, I've been using 

releng/trunk/o.e.foo.releng
o.j.bar/releng
o.j.baz/releng/o.j.bazN.releng
o.e.g/releng/o.e.g.athena.releng

so... it really doesn't matter anymore what we use. I guess we'd want a portal property that points to which releng project to run? 

Closing. Further discussion in bug 253283.