+1 on starting the conversion to git before moving things around Von meinem iPhone gesendet
Am 20.11.2011 um 21:08 schrieb Nicolas Richeton <[email protected]>: > Hi all, > > I fixed tests for composite table on CVS. > I will also commit soon some changes to allow to run the build on OSX. > > The build is still broken because of the 'examples' application which > depends on both stable and incubation widgets. > I think we should extract extensions from the main plugin. At least > extensions which depends on incubation widgets. > > We would have : > org.eclipse.swt.nebula.examples - App + release widgets > org.eclipse.swt.nebula.examples.incubation - incubation widgets. > > We could also do a lot of clean up in the repository > - Delete all releng projects : no longer necessary > - Settle on how we package snippets : one for nebula or one per widget > - Settle on a namespace : org.eclipse.swt.nebula or org.eclipse.nebula > - Remove ghost folders (old or moved plugins) > > The only issue is that CVS prevent us to move files if we want to keep > history and does not allow to remove folders This means that any cleanup will > result in more mess in the CVS exploring view or in CVS Web access. > > To ensure we can do all the refactoring, I think we should move to SVN or git > ASAP. We already discussed of this topic on this list and the choice was git > if I remember correctly. > > Should be start converting the repo right now ? > > -- > Nicolas > > > Le 19 nov. 2011 à 23:09, Wim Jongman a écrit : > >> Hi Nicolas, >> >> Allright this makes sense. I missed the history. >> >> The oscilloscope tests are running now. I switched it to another junit >> version. >> >> Regards >> >> Wim >> >> Sent from my iPhone >> >> On 19 nov. 2011, at 22:21, Nicolas Richeton <[email protected]> >> wrote: >> >>> Hi Wim, Tom, >>> >>> There are several reasons why we have only 2 builds : >>> >>> * When we were building using cron jobs and athena, we had 1 job per >>> widget. As Tom said, it was introducing a lot of overhead when updating the >>> build process or adding a new widget. >>> * With Hudson, we cannot manage jobs directly : creating a new job requires >>> an action from the webmaster. (However, this does to take long) >>> * Eclipse webmasters do not like having 15 builds for a single project. >>> This creates a lot of unnecessary load on serveurs. >>> * As discussed in this list, we are trying to do a stable release of >>> Nebula. This implies releasing several widgets at once. Since we won't be >>> doing separate release, a failing build should be an issue for all >>> committers, not only for the one responsible of this widget. (This is true >>> mostly for the stable build). >>> >>> In my opinion, it would be a great if at some point, each committer has >>> enough knowledge to work on any Nebula widget. This would increase overall >>> quality and speed up development and bug fixes. >>> I think that using only 2 builds will help us to reach that point, since we >>> cannot ignore a broken widget and everyone will be somehow responsible to >>> do the fix (thus work on every widget). >>> >>>> BTW can't one >>>> configure tycho to proceed even if the tests are failing? >>> >>> I think this is generally a bad idea as this would mean that failing tests >>> are a minor issue and they are not. :-) >>> >>> I'll try to look at failing and remaining tests next week (composite table, >>> oscilloscope, and xviewer). Can I update tests which cause issues (based >>> on gallery ones) ? >>> >>> I also requested the reactivation of my shell account so I can look at the >>> download area (just received a mail because we are using 9Gb and quota is >>> 2Gb max) >>> >>> -- >>> Nicolas >>> >>> Le 19 nov. 2011 à 02:28, Tom Schindl a écrit : >>> >>>> Hi, >>>> >>>> Then they have to comment out their tests until they can be run >>>> successful - this how it is done also in other projects. BTW can't one >>>> configure tycho to proceed even if the tests are failing? >>>> >>>> Tom >>>> >>>> Am 19.11.11 02:22, schrieb Wim Jongman: >>>>> Hi, >>>>> >>>>> Let me explain a bit better: >>>>> >>>>> For example, the composite table tests do not run correctly [1]. It is >>>>> not that they fail but for some reason tycho is not happy. Depending on >>>>> who is responsible for the composite table tests, this could take some >>>>> time. Perhaps some days, perhaps some weeks. >>>>> >>>>> All that time, other widget changes cannot release because the build >>>>> breaks. >>>>> >>>>> If we have one build job per widget then the "release job" would always >>>>> just consume the latest successful build for any widget. >>>>> >>>>> Best regards, >>>>> >>>>> Wim >>>>> >>>>> [1] >>>>> https://hudson.eclipse.org/hudson/job/maven-nebula-1.0-nightly/158/console >>>>> >>>>> >>>>> On Sat, Nov 19, 2011 at 1:52 AM, Tom Schindl >>>>> <[email protected] <mailto:[email protected]>> wrote: >>>>> >>>>> Hi Wim, >>>>> >>>>> Am 19.11.11 01:31, schrieb Wim Jongman: >>>>>> I think we need to create a build job per widget. If one widget fails >>>>>> for some reason, the complete build is invalid. >>>>> >>>>> Well the one that breaks the build is responsible for fixing. I really >>>>> don't think that it is pratical to have a build job for each widget. >>>>> >>>>> Tom >>>>> >>>>> -- >>>>> B e s t S o l u t i o n . a t EDV Systemhaus GmbH >>>>> ------------------------------------------------------------------------ >>>>> tom schindl geschäftsführer/CEO >>>>> ------------------------------------------------------------------------ >>>>> eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 >>>>> 935833 <tel:%2B%2B43%20512%20935833> >>>>> http://www.BestSolution.at phone ++43 512 >>>>> 935834 <tel:%2B%2B43%20512%20935834> >>>>> _______________________________________________ >>>>> nebula-dev mailing list >>>>> [email protected] <mailto:[email protected]> >>>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> nebula-dev mailing list >>>>> [email protected] >>>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >>>> >>>> >>>> -- >>>> B e s t S o l u t i o n . a t EDV Systemhaus GmbH >>>> ------------------------------------------------------------------------ >>>> tom schindl geschäftsführer/CEO >>>> ------------------------------------------------------------------------ >>>> eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833 >>>> http://www.BestSolution.at phone ++43 512 935834 >>>> _______________________________________________ >>>> nebula-dev mailing list >>>> [email protected] >>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >>> >>> _______________________________________________ >>> nebula-dev mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >> _______________________________________________ >> nebula-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/nebula-dev > > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
