I just switched the version to 1.0.0 :) But will do the release later, probably during the weekend :)
> well for training, specially its your first release i would not mind > keeping the 1.0.0-M1 flag. Historically, people try to predict too > much into the 1.x release numbers ( compared to 0.x release). But it > really does not matter. Its just important that you can communicate > what you do to the community (release notes e.g.) PLUS being able to > react to issues (make another release, keep improving). > > > On Wed, Jan 19, 2011 at 11:23 PM, Achim Nierbeck > <[email protected] <mailto:[email protected]>> wrote: > > Well, I haven't done the release yet. > I can do a 1.0.0 or even wait if we want to go through a TCK. > > Achim > > > Public servers as explained by Toni should be sufficient. For > > example, my key is available at > > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xECDFEA3CB4493B94 > <http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xECDFEA3CB4493B94> > > gpg --keyserver hkp://pgp.mit.edu <http://pgp.mit.edu> > --send-keys <your-key> > > > > > > > > > > I kinda agree with Toni about the M1 stuff too. I'm not really what > > it means, it kinda looks unstable / unfinised, whereas a 0.8.0 or > > 1.0.0 would look better to me. > > I'd like to get some time to pass the TCK to see if we're missing > > important things, but i doubt I'll get around to do that soon, > but if > > we're quite confident we follow the spec, a 1.0.0 would be even > better > > imho. We can always release 1.0.x later to fix problems, I don't see > > that as a bad sign. > > > > On Wed, Jan 19, 2011 at 22:47, Achim Nierbeck > <[email protected] <mailto:[email protected]>> wrote: > >> there is never a stupid question :) > >> > >> first of all I just think this is just a major step to go from > 0.8.1 release to 1.0.0 which should be worth a M1 as a last > Integration step > >> to just make sure we do have all needed features and bugs fixed > to really call it a 1.0. > >> > >> Regarding your first answer, thank good I'm not at the point of > promoting :) > >> I read the documentation till the end :) > >> > >> So what would be a good place to put the key to? > >> > >> Thanks, Achim > >> > >> ermm.. one stupid question maybe, because i did not really > follow the pax web development recently myself .. why is it a M1 > release exactly ? and not 0.9.9 or 1.0.0 ? Don't tell that its > because Pax Exam 2.0.0-M1 made an example .. ;) > >> > >> On Wed, Jan 19, 2011 at 10:40 PM, Toni Menzel > <[email protected] <mailto:[email protected]>> wrote: > >>> We are using the oss.sonatype.org <http://oss.sonatype.org> > system, which requires us to have the key available "somehwere". > >>> Read this: > > http://www.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/ > >>> -- snip -- > >>> > >>> Distribute Your Public Key > >>> > >>> Since other people need your public key to verify your files, > you have to distribute your public key to a key server: > >>> > >>> gpg --keyserver hkp://pgp.mit.edu <http://pgp.mit.edu> > --send-keys C6EED57A > >>> > >>> Here I distributed my public key to hkp://pgp.mit.edu > <http://pgp.mit.edu>, use –keyserver along with a key server > address, and use–send-keys along with a keyid. You can get your > keyid by listing the public keys. Note that public keys are > synced among key servers. > >>> > >>> Now other people can import your public key from the key > server to their local machines: > >>> > >>> gpg --keyserver hkp://pgp.mit.edu <http://pgp.mit.edu> > --recv-keys C6EED57A > >>> > >>> -- snap -- > >>> Anyway, its being used quite late in the process, when you > actually promote the release to Maven Central (after login into > oss.sonatype org and hit the "promote" button.). Are you on that > point already? > >>> I agree this should have been written on the release wiki page. > >>> Toni > >>> On Wed, Jan 19, 2011 at 10:07 PM, Achim Nierbeck > <[email protected] <mailto:[email protected]>> wrote: > >>>> Hi guys, > >>>> > >>>> I'm stuck at the release process for 1.0.0.M1 for PAX-WEB > right now. > >>>> The Release docu > http://wiki.ops4j.org/display/ops4j/Releasing states that > >>>> a gpg key should be uploaded. How do I get access to the > mentioned > >>>> www.ops4j.org <http://www.ops4j.org> server? > >>>> > >>>> The standard ops4j credentials can not be used. Is this a > result of the hack of > >>>> the ops4j machines? > >>>> > >>>> Please give me some sort of advice how I can go ahead and > release this version? > >>>> > >>>> Thanks, Achim > >>>> > >>>> > >>>> Go for it: bring it on ;) > >>>> Which list ? > >>>> > >>>> On Sun, Jan 16, 2011 at 10:18 PM, Achim Nierbeck > <[email protected] <mailto:[email protected]>> wrote: > >>>>> Hi all, > >>>>> > >>>>> I would like to propose a 1.0.0.M1 for PAX-WEB. > >>>>> Is there any issue open that really needs to be fixed before > we can call > >>>>> it a 1.0? > >>>>> And secondly what do I need to do the release process. > >>>>> Right now only 4 persons are listed to be possible to > release, is that > >>>>> correct? > >>>>> > >>>>> Feedback is welcome :) > >>>>> > >>>>> Greetings, Achim > >>>>> > >>>>> _______________________________________________ > >>>>> general mailing list > >>>>> [email protected] <mailto:[email protected]> > >>>>> http://lists.ops4j.org/mailman/listinfo/general > >>>> > >>>> > >>>> -- > >>>> Toni Menzel || http://okidokiteam.com > >>>> > >>>> > >>> > >>> > >>> -- > >>> Toni Menzel - http://www.okidokiteam.com > >> > >> > >> -- > >> Toni Menzel - http://www.okidokiteam.com > >> > >> > >> _______________________________________________ > >> general mailing list > >> [email protected] <mailto:[email protected]> > >> http://lists.ops4j.org/mailman/listinfo/general > >> > > > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > ------------------------ > > Open Source SOA > > http://fusesource.com > > > > > -- > *Toni Menzel - http://www.okidokiteam.com*
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
