Sorry to insist, but I'd really like to have a definitive answer on this before vdirsyncer is packaged. I suspect that if vdirsyncer makes its way into stable before 1.0, it essentially means I'm forced into long-term support of whichever release is in stable. However, ideally I'd like to only support the latest release of vdirsyncer. If being in stable would really hinder timely updates, I'd prefer vdirsyncer to stay in testing/unstable forever. On Fri, Jan 29, 2016 at 06:37:38PM +0100, Filip Pytloun wrote: > I am pretty new to maintaining official Debian packages but if new > release won't introduce some new dependencies (especially that are not > packaged yet), creating new package version should be almost automatic. > > Of course there's some unstable -> testing -> stable release process, > but unfortunately I have no practical experience with this yet. > > On 2016/01/29 18:31, Markus Unterwaditzer wrote: > > A question: If I release an update of vdirsyncer the day after it is packaged for Debian, how long would it take to reach the repo? Which intermediate staging repos are there that would delay an immediate update of the package? > > > > On 29 January 2016 17:05:18 CET, Filip Pytloun <filip@pytloun.cz> wrote: > > >Hello, > > > > > >I've almost finished packaging of vdirsyncer but it requires > > >dependencies not currently in sid: > > >python-click-log and python-atomicwrites > > > > > >It shouldn't be difficult to package these as well, but any help is > > >welcome :-) > > > > > >Filip > > > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity.
Attachment:
signature.asc
Description: Digital signature