Hi Niclas, > It would be great if you could lead the way on this. > Thanks, I hope to be able to do it :-)
> Perhaps you and others haven't seen our "codebase" guideline; > http://zest.apache.org/community/codebase.html, which contains a nice > diagram on the Git forking model we use. > I already looked at it, but I have to check it better/deeper, thanks for the info ok I'll do the initial setup during next days (as always I need some time, you know :-) ) and post some update. After a quick review, in Pivot sources I had to create a Jenkins-specific folder to isolate some Jenkins-specific stuff, I'll check if needed even here so we can discuss if/where to put it. For updating Gradle to latest, I'll check it later (unless someone will do it before me) ... For the signing key, I have my ASF signing PGP Key (I have to check if it's not expired but I can renew) that could be good. We need also to add our PGP signing keys to KEYS file, you remember ? And then maybe add keys from other Zest PMC Members (at least Release managers). As a side note, for Zest first release here, who will be the Release Manager, you or someone other ? If needed I can help (or I could do it but with Zest-specific help from others :-) ) ... but we have some time for this. Stay well. Bye 2015-06-12 10:43 GMT+02:00 Niclas Hedhman <[email protected]>: > It would be great if you could lead the way on this. > > Perhaps you and others haven't seen our "codebase" guideline; > http://zest.apache.org/community/codebase.html, which contains a nice > diagram on the Git forking model we use. > > > > On Fri, Jun 12, 2015 at 4:31 PM, Sandro Martini <[email protected]> > wrote: > >> Yes, I did a setup some time ago for Pivot (one build per branch with >> default JDK, and another with a more recent JDK, so in total 4 or more >> daily builds). >> >> Zest uses Gradle so all should be doable. >> At the moment Zest is using Gradle-2.2.1, but latest (2.4) is faster, >> what do you think to update (if all builds the same of course :-) ) ? >> >> I think we can start with default branch and default configuration. >> >> >> I can try to take a look, or help someone who wants to do it ... tell me. >> >> >> This is the issue: >> https://issues.apache.org/jira/browse/ZEST-28 >> be free to update/reassign, or move outside the 2.1 umbrella , don't worry. >> >> >> Bye >> >> >> 2015-06-12 10:10 GMT+02:00 Jiri Jetmar <[email protected]>: >> > Hi Sandro, >> > >> > at least for me this is a good idea ! I guess it will be possible to >> > measure aspects like >> > failing tests, coverage, .. in a automated way. >> > >> > Cheers, >> > jj >> > >> > 2015-06-12 9:51 GMT+02:00 Sandro Martini <[email protected]>: >> > >> >> Hi all, >> >> to help with builds (or better to ensure code is buildable, at least >> >> one time per day), what do you think to add a new issue for Jenkins >> >> builds of Zest branches (master, and maybe others) ? >> >> >> >> https://builds.apache.org/ >> >> >> >> >> >> Bye, >> >> Sandro >> >> >> >> >> >> 2015-06-12 2:51 GMT+02:00 Niclas Hedhman <[email protected]>: >> >> > Gang, >> >> > >> >> > as I mentioned else-thread, I would like to push a 2.1 release out the >> >> > door. >> >> > >> >> > >> >> > For this to be achievable, there are quite a lot of small tasks to be >> >> made, >> >> > and I have started to collect those on >> >> > https://issues.apache.org/jira/browse/ZEST-24 >> >> > >> >> > Please help add tasks, and if possible assist any way you can to make >> >> this >> >> > happen. >> >> > >> >> > >> >> > Cheers >> >> > -- >> >> > Niclas Hedhman, Software Developer >> >> > http://zest.apache.org - New Energy for Java >> >> >> > > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java
