Hi list,
It's just a thought, but couldn't the Documentation.txt file be created by create_release.sh automatically when building a distribution kit? I can't see the point of having this file inside the CVS tree since it contains redundant information.
Regards,
Sure!
Marc
Alexander M. Turek a écrit:
Hi list,
It's just a thought, but couldn't the Documentation.txt file be created by create_release.sh automatically when building a distribution kit? I can't see the point of having this file inside the CVS tree since it contains redundant information.
Regards,
Hi
Original message (Alexander M. Turek, 20.11.2003 21:38):
It's just a thought, but couldn't the Documentation.txt file be created by create_release.sh automatically when building a distribution kit? I can't see the point of having this file inside the CVS tree since it contains redundant information.
Good point, I absolutely agree.
Michal
Hi All!
Do we need the 'ANNOUNCE.txt' file in the repository anymore? It sure does look nice, but 2.4.0 is over, right? :)
Objections to remove the file from CVS?
Regards, Garvin
Hi Garvin & list,
Garvin Hicking wrote:
Do we need the 'ANNOUNCE.txt' file in the repository anymore? It sure does look nice, but 2.4.0 is over, right? :)
I think so. :-)
Objections to remove the file from CVS?
How about keeping it up to date and sending a release announcement not only for milestones, but also for every production release? Shall I write a new announcement for 2.5.5?
Regards,
--
Alexander M. Turek rabus@users.sourceforge.net _ __ __ _ _ _ _ __ | |__ _ __ | / |_ _ / \ __| |_ __ ___ (_)_ __ | '_ | '_ | '_ | |/| | | | | / _ \ / _` | '_ ` _ | | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|__, /_/ ___,_|_| |_| |_|_|_| |_| |_| |_| |___/ http://www.phpmyadmin.net
Hi Garvin & list,
Garvin Hicking wrote:
Do we need the 'ANNOUNCE.txt' file in the repository anymore? It sure does look nice, but 2.4.0 is over, right? :)
I think so. :-)
Objections to remove the file from CVS?
How about keeping it up to date and sending a release announcement not only for milestones, but also for every production release? Shall I write a new announcement for 2.5.5?
Regards,
--
Alexander M. Turek rabus@users.sourceforge.net _ __ __ _ _ _ _ __ | |__ _ __ | / |_ _ / \ __| |_ __ ___ (_)_ __ | '_ | '_ | '_ | |/| | | | | / _ \ / _` | '_ ` _ | | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|__, /_/ ___,_|_| |_| |_|_|_| |_| |_| |_| |___/ http://www.phpmyadmin.net
Alexander M. Turek a écrit:
Hi Garvin & list,
Garvin Hicking wrote:
Do we need the 'ANNOUNCE.txt' file in the repository anymore? It sure does look nice, but 2.4.0 is over, right? :)
I think so. :-)
Objections to remove the file from CVS?
How about keeping it up to date and sending a release announcement not only for milestones, but also for every production release? Shall I write a new announcement for 2.5.5?
Regards,
Alexander,
Probably it's me just beeing too lazy, but I think that the release notes we maintain on phpmyadmin.net, plus the quick email sent at each release, are enough.
Marc Delisle
Hi Marc & list,
Marc Delisle wrote:
Probably it's me just beeing too lazy,
Probably :o)
but I think that the release notes we maintain on phpmyadmin.net, plus the quick email sent at each release, are enough.
Removing the file is okay for me. It was just a thought because I liked that file... :-)
Let's have a clean 2.5.5,
--
Alexander M. Turek rabus@users.sourceforge.net _ __ __ _ _ _ _ __ | |__ _ __ | / |_ _ / \ __| |_ __ ___ (_)_ __ | '_ | '_ | '_ | |/| | | | | / _ \ / _` | '_ ` _ | | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|__, /_/ ___,_|_| |_| |_|_|_| |_| |_| |_| |___/ http://www.phpmyadmin.net
-
Alexander M. Turek -
Garvin Hicking -
Marc Delisle -
Michal Cihar