Dne 23.9.2013 15:34, Josef Reidinger napsal(a):
[...]
> Well, I propose different approach to do it only when needed, as there
> is a lot of modules which doesn't have maintainer and that is not
> touched at all, so it doesn't need maintenance branch.
> Maybe it will nicely show usage of modules.

It might sound good, but the problem is if you touch such an "unmaintained" 
module
after like 6 months you will very likely (I'd say almost for sure, see later) 
forget
to create the maintenance branch.

And then after another 6 months it is pretty hard to find the correct commit
backwards for creating a maintenance branch for a bugfix.

Yes, you can checkout the OBS sources and find the last commit, but it's not 
trivial
(checking just the *.changes file may not be enough as there might be just a 
small
fix not mentioned in *.changes...).

Therefore I suggest creating the branch for all relevant (included in openSUSE)
repositories globally.


And here starts the interesting part, I just have checked which repositories do 
NOT
have 12.2 and 12.3 branches and surprisingly the number is quite high (see the
attached files for complete list):

 - 84 repositories do not have 12.2 branch
 - 74 repositories do not have 12.3 branch

(I have manually filtered out some obsoleted packages or product specific (SLE)
packages, but I could overlook something in the quick search so these are 
probably
not perfectly exact numbers, but they still demonstrate the problem quite 
nicely.)

What's worse, even a base package like yast2-core does NOT have the maintenance
branches so it's quite difficult to find the difference between releases or 
since the
last release (e.g. "git log origin/openSUSE-12_2..origin/openSUSE-12_3" does 
not work).

And that's really stupid. We could avoid this by adding the branches globally.

--

Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
[email protected]
SUSE
add-on
add-on-creator
apparmor
autofs
bootloader
branding
control-center
control-center-gnome
core
country
crowbar
dbus-server
devtools
dhcp-server
dns-server
doc
drbd
fcoe-client
firewall
firstboot
ftp-server
hardware-detection
heartbeat
http-server
inetd
installation
instserver
ipsec
irda
iscsi-client
kdump
kerberos-server
ldap
ldap-client
ldap-server
live-installer
lxc
mail
mail-server
metapackage
multipath
mysql-server
network
nfs-client
nfs-server
nis-client
nis-server
ntp-client
online-update
pam
perl-bindings
pkg-bindings
pos-installation
printer
product-creator
proxy
python-bindings
ruby-bindings
runlevel
samba-client
samba-server
scanner
schema
security
slide-show
slp
slp-server
snapper
sound
squid
sshd
sysconfig
testsuite
tftp-server
theme
transfer
tune
tv
update
users
vm
wagon
x11
xml
add-on
add-on-creator
apparmor
autofs
backup
bootloader
branding
control-center
control-center-gnome
core
dbus-server
devtools
dhcp-server
dns-server
doc
drbd
firstboot
ftp-server
hardware-detection
http-server
inetd
instserver
ipsec
iscsi-client
kdump
kerberos-client
kerberos-server
ldap
ldap-server
live-installer
mail
mail-server
metapackage
multipath
network
nfs-client
nfs-server
nis-server
ntp-client
online-update
packager
pam
perl-bindings
pkg-bindings
printer
product-creator
proxy
python-bindings
restore
ruby-bindings
runlevel
samba-client
scanner
schema
security
slide-show
slp
slp-server
sound
sshd
sysconfig
testsuite
tftp-server
theme
transfer
tune
tv
update
users
vm
wagon
x11
xml
ycp-ui-bindings

Reply via email to