Florian Effenberger píše v So 01. 12. 2012 v 13:29 +0100:
Hello,
Niko Rönkkö wrote on 2012-12-01 07:06:
Can someone, please, sort dev-build dailies by branch?
http://dev-builds.libreoffice.org/daily/
Michael M. said on IRC that "that could be done with symlinks quite
easily I guess"
So like:
http://dev-builds.libreoffice.org/daily/libreoffice-3-6
http://dev-builds.libreoffice.org/daily/master
or:
http://dev-builds.libreoffice.org/daily/by_branch/libreoffice-3-6
http://dev-builds.libreoffice.org/daily/by_branch/master
It would be much easier to direct common people to test the right
builds from Wiki for example..
Not all tinderboxes are building all banches so today its behind some
work to find usable build. Luckily(?) there is NOT so many tinderboxes..
I think this is rather a question for the developers, since that machine 
is maintained by them and I don't want to interfere with their way of 
working. :-)
I agree that it would make the life easier because people are usually
primary looking for a particular version.
If someone lets me know what to do, I am happy to, but I'm hesitant to 
changing things on my own, without knowing all development details.
It should be enough to update the path in the script
http://cgit.freedesktop.org/libreoffice/contrib/buildbot/tree/bin/push_nightlies.sh
I could do the change if nobody is against it.
Norbert, others, what do you think about it?
Best Regards,
Petr
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.