On 03/15/2013 01:51 PM, Ed Willink
No. The project description is the project description. The PMI does
capture revisions (using Drupal's support for this), but I have no
intention of leveraging this for the simultaneous releases page.
Once you find your way round, the new PMI provides a better way
for what it does, but I'm very confused.
For instance, once Luna is out, how will it be possible to access
the project description for Kepler? Is there a hidden GIT?
The description I mentioned is the description of the release. This
is part of the release record.
On 15/03/2013 17:28, Wayne Beaton
You can also include your plan information directly on the
release record and start assembling your review information
there as well. There is no specific requirement to do this. You
can continue to do what you've been doing all along if you'd
Currently my project plan is in Eclipse.org GIT
mdt\ocl\project-info\plan_kepler.xml which I can understand.
The PMI has some new location that I do not understand.
Are you doing some magical timestamp comparison to detect which of
the old/new way is in use?
Then you will have two separate copies.The PMI stores the plan
information in a database. Drupal provides some revision control
that can be leveraged here.
What happens if I edit in the PMI, then my colleague edits the
When I did the import of the existing information, I pulled in
project plans where I could find them. It was a one-way process.
You must choose to either continue to run with an XML file, or you
can use the form elements in the PMI. There is no plan to attempt to
Are you automatically updating the XML and performing GIT commits
on my behalf?
cross-project-issues-dev mailing list