Re: 1.3 release soon

  Hi!

Not really any 'showstopper' bugs, and I almost always ask immediately when I 
bump into something... and you usually fix it immediately... ;-)

But one thing that I'd recommend is to make sure that the output of all themes 
create valid markup. Ie. right now I noticed that devblog.bitflux.ch doesn't.

Then there are a bunch of more matter of taste things. Ie. trying to use as 
semantic markup as possible including class/id names. But this could brake 
some of the CSS-themes. As I promised a few minutes ago, I'll at some point 
compile a list of changes which I think would be sensible (but probably not 
in time for the release, well maybe I'll come up with something faster if you 
ask me to...). Then you can apply whatever changes that you think are good. 
But the best choise might be to publish it as a separate theme, to keep 
current CSS-themes intact.

  cheers, Simon


On Friday 25 November 2005 10:16, Christian Stocker wrote:
> Hi
>
> We plan to soon release Flux CMS 1.3. We will most certainly not branch
> that right moment (too much work to maintain 2 branches), but as soon as
> we will bc-break something important or add new - potentially
> "dangerous" - features, which will need more than "rm tmp/* and
> admin/webinc/update", we will branch. No idea, when that will happen.
> But until then, it should be safe to "svn up" from HEAD.
>
> So, the big question now is, is anyone aware of any important
> showstopper bugs, which should be fixed before we release 1.3.0?
>
> chregu
> --
> christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich
> phone +41 44 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71
> http://www.bitflux.ch | [email protected] |  GPG 0x5CE1DECB
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms