Re: schedules Gnus releases
On 4 Apr 2006, Peter S. Galbraith stated:
> Manoj Srivastava <srivasta@debian.org> wrote:
>
>> Upstream is planning on releasing Gnus 5.10.8, and No Gnus
>> version 0.4, in a couple of days. I am soliciting comments on how
>> Gnus packaging should be done for Debian.
>>
>> Sid already contains No guns 0.3, but sets the version as
>> 5.10.6+<blargle> . Shipping Gnus 5.10.8 would essentially mean that
>> people running Sid would have a downgrade, and is probably not
>> desirable.
>>
>> If we ship No Gnus 0.4, the issue is again one of numbering, the
>> reason upstream skipped 5.10.7 is because of us shipping No gnus,
>> in part. I would like to prevent these in the future.
>>
>> So, we have either forcing people running Sid's Gnus to downgrade
>> from No Gnus 0.3+ to 5.10.8, of ship an unreleased version and
>> complicate versioning for future releases. Not a clean path going
>> forward. I am inclined to continue to ship No Gnus, and hopefully
>> Emacs and Gnus shall release soon, or at least before etch, and
>> then etch would release is Gnus 5.11.
>
> I'll admit that gnus version numbers have me baffled. Which is in
> the Emacs CVS repository (and presumably included in
> emacs-snapshot)?
Emacs CVS contains the 5.10.x branch, and the Gnus CVS 5-10
and emacs CVS Gnus are kept in sync. This used to the Oort branch,
and when emacs is release (as Aaron Ucko reminded us), Oort would be
released as Gnus 5.11, and development stopped on Oort.
No Gnus is the development branch, and is destined to become
5.12.X sets of releases.
> When gnus and MH-E that are currently in Emacs CVS are both
> released, mh-e and gnus packages could share icons. Alternatively,
> the mh-e package could depend on the gnus package since it adds much
> (highly) recommended functionality anyway.
manoj
--
I've never been drunk, but often I've been overserved. George Gobel
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: