Hi Jeff, you should read this
- https://www.apache.org/dev/release-signing.html And this page is still more in extenso (4a,b seem only optional or redundant for release signing): - https://cwiki.apache.org/confluence/display/FALCON/How+to+generate+keys+for+signing+the+release You may then add your credentails to maven settings.xml either your mvn-secured password or in another way, cft. https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Setting+up+ssh <server> <id>apache.releases.https</id> <username><uid></username> <password>{XXXXXXXXXXXXXXXXXXXXXXXX}</password> <!-- master-password encrypted password --> </server> Same for apache.snapshots.https .. We may discuss off-list more details, if the archetype RC is ready .. Bon voyage! Best regards, Georg Von: Jeffery Painter <[email protected]> An: [email protected] Datum: 21.02.2018 13:25 Betreff: Re: Antwort: Re: turbine core 4.0.1 release schedule Thanks Georg, I also found the release notes from Apache commons which are well documented. https://commons.apache.org/releases/prepare.html Sorry I didn't have time to work on this. I am leaving for Singapore next week and trying to get everything ready before we leave. It looks like the first step is that I need to generate a GPG key and add it to https://dist.apache.org/repos/dist/release/turbine/KEYS Is there any thing I need to do before adding my keys? Maybe I can help with the turbine-webapp archetype release as a learning process. Thanks, Jeff On 02/21/2018 03:06 AM, Georg Kallidis wrote: > Hi Jeff, > > some "advice" .. currently the "cheatsheet" I use for a release is checked > in here: > https://svn.apache.org/repos/asf/turbine/fulcrum/trunk/README.txt - which > is also the Apache Fulcrum starting page on GitHub > https://github.com/apache/turbine-fulcrum (until we provide a readme.md). > The document should work for Windows and for *nix systems, with some > hints, if no GPG agent is running or not (Windows). Commands may run > without explicit gpg flags. > > For site publication in general check > https://svn.apache.org/repos/asf/turbine/fulcrum/trunk/security/README - > this should be moved elsewhere and > find more hints especially for Turbine site building (lower part with > references) here: > https://svn.apache.org/repos/asf/turbine/core/trunk/README.txt ( > https://github.com/apache/turbine-core). > > You may find there most of what is needed. > > - Georg > > > > Von: Jeffery Painter <[email protected]> > An: [email protected] > Datum: 16.02.2018 13:19 > Betreff: Re: turbine core 4.0.1 release schedule > > > > Hi Georg, > > I would like to learn more about the release process. I will do some > homework this weekend to see what is involved. I have never done it > before, so I may need some advice and guidance along the way. I think > the next big step would be Java 8 as you mention, and I would be up for > helping make that transition happen. > > -- > Jeff > > On 02/16/2018 03:40 AM, Georg Kallidis wrote: >> Hi Jeff, >> >> that´s great! We have to talk through this really .. >> >> Following is, what IMO taking place in the next two, three weeks, based > on >> what could be expected from current state: >> >> Thomas is in the process of preparing Intake, after this I would remove >> the two SNAPSHOTS (one of them already now resolved) in turbine core and >> prepare the release. Building the site may take some more time, but this >> could postponed or prepared all along. And yes, then we are able to >> release the archetype lastly! Do you want to volunteer for the release >> process? No other issues ASAIK! >> >> After this is done the race is opened for the Turbine (Java) 8 IMO! We >> might declare this just plain text - details following .. as reading our >> mailing list we agree on this matter. I have added some comments/hints > in >> pom dependencies, what might be done (+ release of Torque 4.1, which >> requires Java 8). More disrupting changes, which would mean e.g. an > entire >> new configuration building, are probably tasks requiring some more >> (combined) effort. I think Thomas already made some efforts to migrate > to >> velocity 2. But you might have some more insightful thoughts you would >> like to share! We should not forget about changing/adding more structure >> ton the repo (writeable GIT, another branch?). >> >> Best regards, Georg >> >> >> >> >> Von: Jeffery Painter <[email protected]> >> An: Turbine Developers List <[email protected]> >> Datum: 15.02.2018 17:39 >> Betreff: turbine core 4.0.1 release schedule >> >> >> >> >> Hello everyone, >> >> I am pretty deep into building out a detailed tutorial on getting >> started with Turbine 4.0 in Eclipse using the Maven archetype (I am >> quite sure it is a book now instead of a simple tutorial). I was >> wondering when we can expect final releases of Turbine core and the new >> turbine-webapp archetype? >> >> Once Thomas releases intake 1.2.3, is there anything else preventing >> releasing turbine 4.0.1 and subsequently turbine-webapp-4.0 version > 1.0.2? >> Let me know if there is anything I can do to help :-) I am working from >> snapshots at the moment, and it isn't reasonable for me to enlist others >> to test out my walk through until these are released. I would also love >> to share it with you guys for feedback if/when you have time. >> >> Thanks, >> Jeff >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Jeff Painter CEO and Founder of JiveCast Software and analytics, made together http://jivecast.com 301 Fayetteville St. Unit 2301, Raleigh, NC 27601 (919) 533-9024 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
