On May 13, 2004, at 2:23 PM, Stephen Colebourne wrote:
I am opposed to adding snapshots to ibiblio, as I have seen it create isues.
IMHO ibiblio should be released/stable code only.
Can you be more clear? I think ibiblio snapshots are great and would hate to see them go away. Think of all the projects out there that are using apache snapshots that would have to add the apache repo to their project. Not only is this a lot of traffic to apache, I think it also sets a bad precedent for other projects. Think of a project using a lot of snapshots and they have to add every small project's repo to the repo list (which may also add to the apache traffic as maven has no idea which repo may have the snapshot, so it tries them all in order) Anyway I'm rambling now.... I am curious about the issues this creates.
Part of the problem was a bottleneck in getting new and updated Apache projects
onto ibiblio. There also is a certain degree of snapshot clutter on ibiblio.
Especially since ibiblio is only accessible to certain people, I think it makes sense
for it only to contain releases, and to have the snapshots at Apache. The traffic
issues could probably be handled by the mirrors, if it isn't already.
I also don't see adding the Apache repo to a properties file as a big deal -- especially
when compared with the chaotic and sluggish nature of the Apache-ibiblio situation,
which seems to have been improved greatly with this new system.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
