[Bug 5863] New: automating binary packages build for each release
Wine Bugs
wine-bugs at winehq.org
Sat Aug 5 04:56:32 CDT 2006
http://bugs.winehq.org/show_bug.cgi?id=5863
Summary: automating binary packages build for each release
Product: Wine
Version: 0.9.18.
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-ports
AssignedTo: wine-bugs at winehq.org
ReportedBy: jerome.bouat at wanadoo.fr
I wonder if binary packages could not be automatically build each time a new
wine version is released.
I mostly test applications running with Wine. I always have to wait for binary
packages before I can test a new release. At the present time, the delay before
I can test is made of the delay that the binary package maintainer needs plus
the delay that I need according to my diary.
What already appened to me (dates are not true) :
- day 1 : A developper asks me for a new test
- day 7 : I see the message and check for a new release.
A new version was released at day 6
but no binary package is yet available.
I wait the binary package.
- day 12 : A new binary package is build.
- day 15 : I see that a new package is available.
- day 21 : I have time to perform the test
but I see a new release is available.
Thus I wait for a new binary package.
According to possibly side effects of one bug fixing, this highly decreases the
global wine bugs fixing efficiency.
I mean the binary package maintainer would always have a key role. When the
maintainer is not available, a default package could be generated with the
specification file of the latest release (but the version number). You could
wait 1 day before you automatically generate the binary package. This give a
chance for the maintainer to proprely generate its own one.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the wine-bugs
mailing list