[Entagged-devel] New release to be done :)

[<ra...@wo...>]

Good !

Now i've somthing to ask you, can you do the release yourself :D ?

I won't have time to do it tonight, i really must redo some exercises 
for my exam tomorrow.

Here are the "instructions", if you don't feel to do it, simply don't, 
and i'll do it tomorrow or something, else you can do it and learn so 
that you can also do it in the future :)

1) Update changelog, and version numbers in the build.xml file
2) "cd ENTAGGED_DIR"
3) run "ant update-doc"
4) commit changed files (eclipse will do it)
5) run "ant package"
    run "win32-installer" (*see PS.)
    This should produce 3 files: Entagged-tageditor-xx.{exe,zip,tar.gz}
(Optional: When update needed for audioformats or freedb (not needed))
6) "cd audioformats"
7) run "ant"
    This should produce 2 files, audioformats jar and tar.gz file

You can now run the rsync.sh script in the entagged-website directory, 
that will update the website's changelog, faq, etc... (it works via ssh, 
so you will have to use your sourceforge login an pass)

Now we're ready to upload to sourceforge:
8) Connect to
FTP host: upload.sf.net
(no need to login, it is anonymous, remote dir should be "/incoming")
9) Upload all the files we created before

Now we have to create the entries in sourceforge:
10) go to sourceforge project page 
https://sourceforge.net/projects/entagged/
11) Go to Admin/File Releases
12) At the bottom, click Add Release in the wanted category
13) The release name is something like "v0.17"
14) Now you have the release setup page
     - Paste the changelog (of te current version only) in the textarea
     - Preserve the preformatted text, so it won't be dsiplayed
       In one line.
     - Select all the files that need to be uploaded for that release
       (tageditor files, or audioformats files, etc)
     - Then you must edit each file one by one, setting 
"Platform-indeendant" and the correct file type (like .zip or .jar or 
source .gz) (and of course for the win32 installer choose "i386" and 
win32 binary)
     - Finally send the mails to the peaople watching for the project
     - You can check if everything went fine by going to the files 
section of sourceforge project page.
15) Now you can hide the previous release, to do that:
  Go to Admin/FileReleases/Edit Releases choose the one to hide, in the 
properies you have a pull-down menu to choose from active or hiddden, 
choose hidden then apply the changes, it should have disappeared from 
the Files section.

These are optional i can do it later, but so you have a global view:
16) Post a little news on the Summary page saying that we released 
something (look at the previous ones)
17) Send a mail to <ent...@li...> mailing list
18) Go to freshmeat, and signal a new release by uploading a little 
changelog and incrementing version number. (maybe you won't be able to 
do it because i'm the owner of the project, and i don't think you will 
have permissions to do that)

Here is it, I think it is all i do, i hope i didn't forgot aything, if i 
did tell me, i'll be watching my emails

See you !
Raf

PS. Maybe you won't be able to run this ant task, that's because it 
needs the nsis installer from nullsoft to generate the installer. I'm 
running it with wine under linux, so i had to install wine, download and 
install nsis software from nullsoft with wine.
If you can't do that, i'll generate and upload the win32 installer for 
you, just tell me..



Christian Laireiter wrote:
> Hey,
> 
> Now it should be safe to delete the .entagged directory, or even
> modifiy the workingdir to a non existing folder.
>