Humm.. but why in the world would you put it as active ?
also, don't forget, what packagers you want to notify ? 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...
you see, we need 1h15 to do all that, there is no 'announce it to
packagers', anyone can do the windows binary in a few seconds,
especially if we switch to the nsis installer which works with a script,
so is a lot easier to configure than bitrock...
for mac, Jerome usually has it all prepared so he just updates a folder
and a single click makes it into a .dmg (correct me if I'm wrong) and
for autopackage, the same, one command and we're done...
no hassle...
no wait...
KKRT
On Wed, Jul 12, 2006 at 09:17:24PM +0200, Sander Hoentjen wrote:
On Wed, 2006-07-12 at 10:35 -0400, Youness Alaoui wrote:
On Wed, Jul 12, 2006 at 08:16:55AM +0200, Harry Vennik wrote:
I agree 100%. We just shouldn't do this anymore. We should just offer the
source package and the Windows and Mac binary packages, and the autopackage
for Linux. The packages for the various distros will be done by the distros,
and if the distro doesn't include amsn, some volunteer may also create it
after the official release date, we should not wait for it. Maybe we should
not even wait for any binary packages at all, and announce a release like:
Release .... is out! You can now download the source package from ... and as
soon as possible binary packages will also be published for Mac, Windows and
Linux (generic autopackage). Linux distribution-specific packages are not
created by us, but many distros include aMSN themselves, and will soon
provide a package of this new release.
i would disagree.. as much as I want to shorten the trouble for us, I don't want to make it more difficult for
our users either... the windows/mac/AP packages MUST be available before announcing the release...
howtos for other distros should also be available.
KKRT
Then what about this:
step 1: We tag, create tarball, upload tarball, put it in file release
as active (not hidden), (we notify packagers?)
step 2: We create binary packages and add them to the release
step 3: we change the website, announce the release
step 4: ???
step 5: profit!
-------------------------------------------------------------------------
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
_______________________________________________
Amsn-devel mailing list
-------------------------------------------------------------------------
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
_______________________________________________
Amsn-devel mailing list
