Message-ID: <1446105556.9302.26.camel@df1844j>
Subject: Re: [alpine-devel] v3.3 feature freeze
From: Leonardo Arena <rnalrd@gmail.com>
To: vkrishn4@gmail.com
Cc: alpine-devel@lists.alpinelinux.org
Date: Thu, 29 Oct 2015 08:59:16 +0100
In-Reply-To: <201510291311.01965.vkrishn4@gmail.com>
References: <20151022180104.1feeb73a@ncopa-laptop>
	 <20151026101227.2e9e3058@ncopa-desktop.alpinelinux.org>
	 <1445872834.3455.43.camel@df1844j> <201510291311.01965.vkrishn4@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-J5gVS6UfV0OTog/xgcg8"
Precedence: list
Mime-Version: 1.0


--=-J5gVS6UfV0OTog/xgcg8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On gio, 2015-10-29 at 13:11 +0530, V.Krishn wrote:
> > On lun, 2015-10-26 at 10:12 +0100, Natanael Copa wrote:
> > > On Fri, 23 Oct 2015 03:04:36 +0530
> > >=20
> > > "V.Krishn" <vkrishn4@gmail.com> wrote:
> > > > > Hi,
> > > > >=20
> > > > > We now need to stop working on new features for the v3.3 release =
and
> > > > > concentrate on wrapping things up for v3.3 release. Testing and
> > > > > fixing bugs.
> > > > >=20
> > > > > A few questions:
> > > > >=20
> > > > > Can we make the 'lua' package be lua5.3? I think everything that
> > > > > needs 5.1 should have depends on 'lua5.1' instead of 'lua'.
> > > > >=20
> > > > > Can anyone help with upgrading llvm-3.7 and clang?
> > > > >=20
> > > > > Can anyone help with upgrade xen to 4.6?
> > > > >=20
> > > > > I'd like to move as much ruby stuff as possible to community, can
> > > > > someone help with that?
> > > > >=20
> > > > > Are there anything else that needs cleanup for v3.3?
> > > >=20
> > > > Any thoughts on:
> > > > 1. All desktops except one that we want to keep as default and read=
y to
> > > > jump on it to fix when update available or broken.
> > >=20
> > > You mean move to community?
> > >=20
> > > I'm all for moving as much as possible to community.
> > >=20
> > > The question was more general, what more cleanup, more than just move
> > > stuff to community, are *needed* before v3.3. Eg the critical stuff,
> > > the things we can not forget.
> > >=20
> > > > 2. Web application like drupal, phpmyadmin, owncloud i.e pkgs that =
does
> > > > not require compiling and are sometimes more easier to install by
> > > > downloading the orig tar and just uncompressing in web-folders.
> > >=20
> > > What about those packages?
> >=20
> > I think we should move to community the packages which don't have stabl=
e
> > and maintained releases. This is not the case of ownCloud since is
> > maintained for 1,5 years after release. For example v6.0.0 was released
> > in Dec. 2013 and last update was 6.0.9 on July 2016. v7.0.0 was release=
d
> > July 2014 it's still actively maintained.
> >=20
> > I think it's handy to have web applications packages for run-from-RAM
> > installations. Also upgrade of packaged web application is faster then
> > tar-based installations.
> >=20
> > Not sure about drupal maintenance policy, and may be phpmyadmin can be
> > likely moved.
>=20
> Criteria is not upstream stability release but,
> 1. Does these pkgs' normal updates get backported ?
> 2. If we decide fitting main is one CD or two do we want them in main the=
n ?
> 3. Pkgs like these are easy to maintain and maybe tagged/delegated to new=
 or=20
> less experienced maintainers.
> 4. Note, there is no stopping for main devs in maintaining community pkgs=
.
>=20

I think to it's one of the relevant criteria. Maintaining a package in a
stable Alpine branch, when upstream does not provide maintenance
releases, puts a load on the Alpine package maintainer that needs to
backport the security patches at least, and possibly other bugfixes too.

So I think one of the main questions to determine whether the package go
to main/community is:

- Is the maintainer willing to ensure that package foo-1.1.0 will have
~2years of security fixes/critical bug fixes available for version 1.1?
If yes, stay in main, if no, go to community, where you are free to bump
to version 2.x.
Or did I get the purpose of community repo wrong?

- leo

--=-J5gVS6UfV0OTog/xgcg8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAABAgAGBQJWMdHUAAoJELAPckZGG2T6WQkH/RakP2ZtyhJWN+Q48ymkFGz9
ZncTV5+wMHoxJIWbpGgb+z83WUqjgNZg1+dxRw+IXKsdczZlbPm+D8H6EzQOKVlE
33ef6MnGTC/FMFXjIv9NkZnbsInKhZRm5kT/FRFSkM6t06OGgDjQJ3bPIlt9btki
DU2KF2WGsP9XukI5sBYc9hXHag2yxsdU/sINWCfC/sCKQDUzC691YCvbHPQUpDhG
9YirIGOBoSLO7yQevvTdVXYytIwdnU+4NZTFck0p3kGbetHg3RN2oFuJkyWmDXb8
U91ylsRftodlza7EcfOWqDKGECMcwHasZLcJ2aeZul8hTjdULXRqYYfH7n2hkQc=
=i7pP
-----END PGP SIGNATURE-----

--=-J5gVS6UfV0OTog/xgcg8--



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---