Hi Todd, > Also, I think this issue is distinct from the points Greg made about > the README and RELEASE-NOTES. I think we should address those points > for this release, whereas I think we should talk this one out and come > up with a strategy for 1.3, but the graffle files should ship with > 1.2. Any objections? No objections from me.
>> This all comes on the back of me working on a Pivot release management >> document that I'll check into SVN so that others can act as release >> managers in the future and have a well-documented procedure to follow. This could help a lot. >> Can the Eclipse files move, or would that mess with their function? >> If they can move, then maybe we create a single folder that contains >> everything that we exclude from releases...? Eclipse projects needs them in root of any project, so I think that moving them is not the best for anyone get sources from Subversion to see/use them for example from Eclipse. But you have reason, we have to see what to do for any file to exclude from releases. Proposal: hiding to release all files that starts with . (like eclipse files) and the same for directories (so some script could do this work any time necessary) ? Bye, Sandro
