On Friday 16 Dec 2011 06:26:11 Arne Babenhauserheide wrote: > Am Donnerstag, 15. Dezember 2011, 16:26:59 schrieb Matthew Toseland: > > On Wednesday 14 Dec 2011 18:15:42 David ?Bombe? Roden wrote: > > > I?m not quite sure how to respond to this as I have received NO > > > INFORMATION WHATSOEVER about what ?make a test build? actually entails. > > > Do we have a build environment on remote hardware or do we simply build > > > on local machines? Is there some special script? Does anything have to > > > be signed, and with what key(s)? What about installers, for Windows and > > > the headless one? How to put it somewhere other people can get it from? > > > Do we have some announcement system on the website? Should news about > > > updates go there at all? What about access to the GitHub repositories? > > > > You agreed to assemble a tree of stuff to test. > > I assume there was some unclear stuff concerning that? > > Let?s all relax a bit. While he?s retaking math stuff, Toad will have > different > activity patterns. So let us do this step by step. > > 1. Fork the repo > 2. Create your own review branch > 3. Merge reviewed changes > 4. Create a jar and aask people to test it on Sone and in IRC. > 5. After you did multiple test-jars that way, ask Toad to integrate it so we > can do > $ ./update.sh test bombe
ArneBab is right. What he means by the last step is we should create a mechanism by which half-trusted parties - not necessarily Bombe - can create test builds and use the official infrastructure. Once a build is tested, *someone* can release a final build. But the hard parts are all the bits leading up to the release - assembling patches, releasing a test build, gathering feedback etc. I'm happy to give Bombe rights to do a full release, he's been around for a long time and has made some important contributions. But given that *there isn't anything to release right now*, I don't see that it's urgent: You shouldn't wait for the keys, you should get on with the important parts. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20111217/022734eb/attachment.pgp>
