Hi Stefan, alright. I just put this issue on our long list of possible improvements (*). But since this doesn't hurt much at the moment it got a low priority and is not worth spending working time.
Franz (*) This list is evolving rapidly and currently manifests itself in a sheet of paper. I'm going to use this list to formulate our status quo in order to work out a strategic roadmap. When the time has come I'd be exited to share and discuss this roadmap with all of you Saros developers. -----Original Message----- From: Stefan Rossbach [mailto:srossb...@arcor.de] Sent: Thursday, May 10, 2012 12:08 AM To: zie...@inf.fu-berlin.de Cc: 'Saros' Subject: Re: [Dpp-devel] Commit History is broken Hi Franz, I'm not sure whether your phrases "great improvement" and "very good job" are to be taken ironically ... This was not ironically, this is one of the greatest changes, you can no longer ship in code that will not compile or where JUNIT test will fail. Yes you are right, this is fine grained stuff, but Jenkins supports a tracking mechanism. E.g just look at the STF Tests, you can choose any "build" (regression) and will it redirect you to the change log of the artifacts that were involved in that "build". Currently the Whiteboard and Nebula does not get many updates, so it would not matter. All information is still present, but it is now a little bit harder to figure out, why something might have failed. Thats all. Regards, Stefan Am 09.05.2012 10:57, schrieb Franz Zieris: > Hi Stefan, > > due to some technical limitations a perfect migration from SVN to Git is not > feasible (contact Holger, if you are interested in the details). What kind of > flaws do you mean when you say that "the commit history is broken"? From a > developer's point of view, I can checkout any specific version at will and > even for someone who is *really* interested in a fine grained and accurate > commit history the old SVN repository is still online and could be copied any > time. > > Additionally I'm not sure whether your phrases "great improvement" and "very > good job" are to be taken ironically since they stand under the headline "XYZ > is broken". Could you please make your mail's actual point a little bit > clearer? At least for someone thinking as slow and heavy-handed as I do? > > Thank you in advance! > > Franz > > > -----Original Message----- > From: Stefan Rossbach [mailto:srossb...@arcor.de] > Sent: Wednesday, May 09, 2012 2:13 AM > To: Saros > Subject: [Dpp-devel] Commit History is broken > > During the migration from SVN to GIT, the commit history of separate > components (Saros, Whiteboard) > were / are still broken. > > You will always read the whole changelog for any Jenkins Job, even if > the build for this component has > not affected any files of this Job (e.g you will read changes in the > Whiteboard that are made to the > Saros Plugin). > > Maybe we could fix that in the future, but at least CI is now performing > a very good job. > > You get an auto -1 if your patch would not even compile and a 0 if you > broke existing test cases. > > Thank you Holger for this great improvement. > > Regards, > Stefan > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Dpp-devel mailing list > Dpp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dpp-devel > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dpp-devel mailing list Dpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
