Yes, I am aware about this issue. However my account stopped working and I need to take it to INFRA. Will take care about this in a day or two: thanks for the reminder.
If anyone feel like getting an account on the Apache CI and fixing the build - please do so by all means! Cos On Thu, Jul 09, 2015 at 12:31PM, Alexey Goncharuk wrote: > It looks like we forgot to change the nightly builds trigger. The website > link > https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/ > points to the build based on sprint-2. > > 2015-07-06 12:00 GMT-07:00 Konstantin Boudnik <c...@apache.org>: > > > Looks good - thanks for putting this together! > > > > Cos > > > > On Mon, Jul 06, 2015 at 06:11PM, Yakov Zhdanov wrote: > > > Igniters, > > > > > > As it has been discussed, we are applying an updated Git policy which > > > should be more flexible and transparent that we have now. > > > > > > Process is described here: > > > https://cwiki.apache.org/confluence/display/IGNITE/Sprint+Process > > > > > > I would also put points here (taken from the page above) > > > > > > - Master should become the development branch for the next release > > > (current sprint). > > > - Whenever current release (sprint) goes to QA, new branch should be > > > created from master. This way master can be used to develop > > functionality > > > of the next release. All release fixes get merged to release branch > > and > > > then to master. > > > - All individual ticket branches should be created off of the master > > > branch (or release branch if one exists - in this case changes get > > merged > > > to release branch and then to master branch). > > > - Git tag should be created for every release. > > > - All CI tests must pass before the merge of ticket branches to the > > > master (or release) branch. > > > > > > ignite-sprint-7 branch will be removed soon. > > > > > > Please let me know if anyone has questions. > > > > > > --Yakov > >
