Re: [cdesktopenv-devel] Proposing an official release in two weeks

Sat, 23 Jun 2018 18:04:55 -0700

Ah, yes, I am quite familiar with Debian's packaging and release policies from a user's perspective.  ‎ I meant, do you need to package a stable release of the software in question? Example: Our stable release is 2.2.4; must you package that, or can you package 2.2.4a (or even master)?

I don't think there are restrictions like that, but I wasn't sure.‎ The Debian folks have some interesting ideas about things sometimes.  =)

I'm just trying to understand in what way the release schedule might impact your efforts at packaging for Debian, if any.


-mrt
From: Chase
Sent: Saturday, June 23, 2018 18:47
To: Matthew R. Trower
Reply To: Chase
Cc: Chase via cdesktopenv-devel
Subject: Re: [cdesktopenv-devel] Proposing an official release in two weeks

Not initially, from the debian wikipedia page:

Initially, an accepted package is only available in the unstable branch.[111] For a package to become a candidate for the next release, it must migrate to the Testing branch by meeting the following:[223]
  • It has been in unstable for a certain length of time that depends on the urgency of the changes.
  • It does not have "release-critical" bugs, except for the ones already present in Testing. Release-critical bugs are those considered serious enough that they make the package unsuitable for release.
  • There are no outdated versions in unstable for any release ports.
  • The migration does not break any packages in Testing.
  • Its dependencies can be satisfied by packages already in Testing or by packages being migrated at the same time.
  • The migration is not blocked by a freeze.
Once in testing, the debian devs will then determine when they want to release and then freeze testing and put it into the release.

Thank you for your time,
-Chase


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On June 23, 2018 5:57 PM, Matthew R. Trower <d...@blackshard.net> wrote:

I ‎would think we should cut new releases when we are ready to do so, rather than after an arbitrary amount of time. Some projects (ex. Debian, Firefox, much commercial software) that have very frequent commits benefit from a set release schedule.  CDE has considerably‎ less churn to it, so we should release when we have accumulated a certain degree of substance --- whenever that may be.

Of course, I think we accumulated that substance long ago.

We could perhaps consider more frequent dev releases between‎ stable releases? That would help show activity if necessary, without potentially reducing stable releases to vaporware.

By the way, I don't know the packaging requirements for Debian... are you required to package a "stable" release?


-mrt
From: Chase via cdesktopenv-devel
Sent: Saturday, June 23, 2018 16:48
To: Henry Bonath
Reply To: Chase
Cc: CDE development
Subject: Re: [cdesktopenv-devel] Proposing an official release in two weeks


My vote is for a new release, however I have my reservations on waiting another 1-2 years for the next release. I would like to get the debian package out as soon as reasonably possible, so could we switch to a release schedule of roughly 6 months from now on? That way people don't think we are a dead project.

Thank you for your time,
-Chase


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On June 22, 2018 8:02 PM, Henry Bonath <he...@thebonaths.com> wrote:

Yes from me as well.
Great work everyone!

On Fri, Jun 22, 2018 at 9:00 PM, Christopher Turkel <turkel.christop...@gmail.com> wrote:
I vote yes.

On Fri, Jun 22, 2018 at 8:56 PM Matthew R. Trower <d...@blackshard.net> wrote:
Affirmative.

-mrt
  Original Message  
From: Jon Trulson
Sent: Friday, June 22, 2018 17:55
Subject: [cdesktopenv-devel] Proposing an official release in two weeks

As the title says, I'd like to propose a "stable" release of CDE in two
weeks.

cde-next will be merged into master after release.

Objections? Affirmations?


--
Jon Trulson

"Fire all weapons and open a hailing frequency for my victory yodle."

- Zapp Brannigan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to