On Sun, 2011-01-30 at 23:34 +0530, Rahul Amaram wrote: > Hi Adam, > Thanks for the response. I missed out the submitters email id. I am > working on a fix and should be submitting tomorrow. > > I do understand that it is very unlikely that this fix can get into > squeeze initial release taking into consideration that it is likely to > be released on Feb 6.
/5/th ;) If you can get your sponsor to upload a package containing just the fix for this bug tomorrow, then there's a reasonable chance of it getting in. > I am a new (sponsored) maintainer and really not aware on how to handle > this. I really don't think this bug is grave as it affects only a part > of the calendarserver and most of the important features seem to be It causes people to lose data, which fits the definition of grave. > running fine. Anyway, I was wondering how do I get this fix into > squeeze? Should it be done via security updates? If we decided that this bug was ignorable for the initial release (which we haven't currently), then a fix would go via stable-proposed-updates as part of a point release. This isn't a security issue, so fixing it via security would be inappropriate. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
