http://people.apache.org/repo/m2-ibiblio-rsync-repository/ For snapshots, we only publish to - http://people.apache.org/repo/m2-snapshot-repository/
Just make sure you follow the ASF Legal guidelines at - http://www.apache.org/legal/src-headers.htmlespecially the part about license/notice/disclaimer files, as we always seem to need updates for our releases...
If you have any crypto code included in your jars, then you'll need to take a look at http://www.apache.org/dev/crypto.html and submit the required paperwork before publishing any new releases.
BTW - I'm not an expert on this, but just trying to give you some pointers...
-Donald Dave wrote:
Sounds like we are in general agreement, which is good because I'd like to get a 4.1 milestone build out ASAP. More comments inline below... On Feb 5, 2008 12:51 PM, Craig L Russell <[EMAIL PROTECTED]> wrote:On Feb 5, 2008, at 6:01 AM, Dave wrote: Other projects call these builds snapshot releases. There is even infrastructure in place to support snapshot releases in maven, for example.* Tagged in SVN+0 It's not obvious that this improves our ability to track down issues. If it only shows up on a milestone build and not after, does it matter?Yes, that is true. I would like to be able to reproduce milestone builds, but all we really need is an SVN rev number for that -- and the SVN rev number is now baked into the builds.And can we streamline the voting process so that it does not take months to also get a milestone release out. How can we streamline the process? One way is to NOT require a formal vote for milestone buildand instead just use lazy consensus.Don't even vote. Just publish it.Good, but just for the purpose of coordination, I think the person making the milestone should at least say "I'm going to make a make a milestone build this week, anybody object?" And if nobody objects in a day or so, they should proceed with the build. - Dave
smime.p7s
Description: S/MIME Cryptographic Signature
