From: Earnie B. <ear...@ya...> - 2003-05-17 19:37:11
|
Mohan Embar wrote: > Hi All, > > Now that I'm here, I'd like feedback on your expectations on how > I can best help out. Aside from participating in the development > discussions, what should I be doing with my file release privileges? > I've just modified the file release pages so that the public versions use the SF ``package'' as a category. I created five categories, Current, Previous, Candidate, Snapshot and Purposed. Under the categories I use the basename of the package for the SF ``release''. The package files are typically named similar to foo-major.minor.patch-yyyymmdd-MingwPackageSubversion.tar.gz for the released snapshot and candidate binary distribution and foo-major.minor.patch-yyyymmdd-MingwPackageSubversion-src.tar.gz for the source file snapshot and candidate release. A typical Current release will have a file name similar to foo-major.minor.patch-MingwPackageSubversion.tar.gz for the binary release and foo-major.minor.patch-MingwPackageSubversion-src.tar.gz. That may change as the developer sees fit as you can notice in the FRS pages. IIRC, Danny just likes the version I listed for the snapshot above and move files from one package/release to another. > Based on what Danny and Ranjit said, it doesn't sound like I want > to be releasing random snapshots, given that files apparently can't > be deleted off of SF once they're uploaded. > Yes. See http://prdownloads.sf.net/mingw for an example. > It also sounds like you all are contemplating a separate gcc source > location in CVS. What would be the rationale behind this? To provide > a repository for our collective patches? > Only if it is beneficial for you and the development of GCC tools. > I don't have tons of free time, but would be happy to help in any way > I can to the extent of my availability. > A ``How to gcj in MinGW'' would be nice. > Thanks again for having me. > Thank-you for joining the group. Earnie. |