Discover (along with our other open-source projects) has been moved to a dedicated team at Progeny, so we should no longer have to rely on the "spare cycles" development model. (See http://platform.progeny.com.)
So, the pace of Discover 2 development should pick up shortly, and in the meantime, we've talked about doing a Discover 2.0.2 release and uploading it to Debian within the next few days. That would probably ensure the smoothest transition, if you haven't already uploaded something (aside from the udeb).
If you send your patches to discover-workers, we could probably do a Discover 2.0.3 release shortly thereafter, with the hope that we can get into a good release rhythm with help and feedback from the d-i folks.
Sound good?
-Ian
Branden Robinson wrote:
On Wed, Jan 21, 2004 at 05:11:58PM +0100, Gaudenz Steinlin wrote:
Am Mit, den 21.01.2004 schrieb Branden Robinson um 16:17: I did not know whom to personally contact. So I decided to send this mail to [EMAIL PROTECTED] and [EMAIL PROTECTED] in the hope that the relevant people at progeny receive it.
discover-workers will suffice. :)
Would it bother you guys terribly to do this as a pre-approved NMU? We can merge the changes back into our SVN repo.
I would be glad if this is merged back to your SVN repo. Is it possible to arrange write access to it or do you want to merge the changes back yourself?
I think our company policy is to manage such things ourselves.
The sources should always be available in the Debian archive, but we can
provide patches if you like.
Patches would be ideal. They're easy to merge. :)
Once LinuxWorld is off our plate, let's see if we can't keep pace with your needs vis a vis Discover 2, and re-evaluate the maintainership issue in 4 weeks or so.
Does that sound reasonable? Your plan sounds good to me, and like what was already discussed, so it doesn't sound very disruptive to previous expectations.
Yes this is OK and reasonable. I just wanted to make sure that this upload is approved by progeny. I have put [EMAIL PROTECTED] in the maintainer field of the udeb-only upload. Should this stay as it is atm or should I put [EMAIL PROTECTED] there?
I suggest changing it to "[EMAIL PROTECTED]".
And one last question: To make the package build on non-i386 archs I had to copy the kernel pcmcia headers into the package source. I have done this in a sperate directory for now, but the most clean solution seem to me to have them in the same directory as the discover pcmcia stuff as normal non-system headers. Would you accept a patch for that?
I'd like to get some other opinions on this. Eric, are you still subscribed?
-- Ian Murdock 317-578-8882 x133 (office) 317-250-0117 (mobile) http://www.progeny.com/ http://ianmurdock.com/
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
