On Thu, 2006-07-13 at 11:02 -0400, Youness Alaoui wrote: > On Thu, Jul 13, 2006 at 02:44:46PM +0200, Sander Hoentjen wrote: > > On Wed, 2006-07-12 at 22:54 -0400, Youness Alaoui wrote: > > > Humm.. but why in the world would you put it as active ? > > Because the packagers can then get it more easily > they should be able to get it with the svn export and don't tell me a > linux package maintainer doesn't know how to use a 'svn export ... ' > command, even n00b can do that...
For Fedora (and I guess for more distro's?) part of the requirements is that the md5sum of the tarball in the package matches the md5sum of the upstream tarball. This means the package can only be created from the official released tarball. (Yes if you have a good reason you can say why you don't use a released tarball, like only cvs/svn version is working properly) > > > > also, don't forget, what packagers you want to notify ? > > The official disto packagers (like me, but i am a bad example because i > > am also a dev) > oh yeah, but is it our job to notify them or is it their job to follow > up with the packages they maintain ? also, when we release, in > sourceforge there is a button that we can press which will notify all > 'listeners' who are waiting for an update of the package... so package > maintainers should be listening for it and we'll announce it to everyone > this way with SF system anyways... Yes, that is a good way to notify the packagers, we shouldn't forget to press this button though, that is my point. You can't expect packagers to have a look at all their packages home pages every day to see if a new version is released.. > > > > in theory, it > > > would go as : > > > 10:00 : decide to release > > > 10:15 : tag the release, export and create tarball > > > 10:30 : someone on windows launches a script that creates the > > > windows installer > > > 10:45 : upload to SF and create the release version > > > 10:55 : 'makeinstaller' and create the AP release > > > 11:00 : Jerome finished creating the mac binaries (he had 45 minutes > > > already) > > > 11:05 : we have the AP, windows and Mac binaries uploaded, we set the > > > release as active > > > 11:15 : we finished setting up the news page and updating everything > > > that has to be updated... > > But (almost) none of the mirrors work yet. > > yeah true, but anyways, what I meant was that we don't need to wait > days/weeks before we can release, we'll wait a few days for the mirrors > to sync, but it's not as critical as waiting 1 month for packages to be > created > We agree here > > > > > > you see, we need 1h15 to do all that, there is no 'announce it to > > > packagers', > > Don't forget a lot of linux users just update their system when new > > updates arrive, and those are done by packagers > > > > > yes, and are we part of the team of FC5 ? or debian ? or gentoo ? no, it > is not our job, if a distribution is not good enough to keep up to date > versions in its repositories, then it's not our problem. > I'm not against you, you are right and we both know it, what I'm trying > to say is that it's not our responsability, it's the distro's. well i am part of the fedora team :P But you are right, it is their responsibility, but we can still make their life a bit easier by providing the source tarball as soon as possible. (Indirectly we make our own life easier because we won't have questions like: it has been 3 weeks since amsn version X is released, when will my distro Y finally have this version?) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
