I think that we would be kidding ourselves if we call that release
2.7.5, since a fair bit of code has changed since 2.7.4 and especially
considering that what we imported in the hg repo had already been
extensively developed by Geeklog.jp group. It would also be misleading
for users, as they might expect just a few small bugfixes compared to
2.7.4, but they will be getting a (potentially more unstable) feature
release...
I think that we should call it a major: 2.8.0.
As far as dates go, I don't have any new features to check in and so I'd
be happy with a feature freeze next Monday, 9th of May. Followed by a
few rounds of testing, one week at a time and release around beginning
of June.
What about more long term plans? I'm thinking that we should explicitly
state what versions we will be officially supporting and for how long.
Since we are pretty small right now, I would say that we should not
support anything older than our next release (2.7.5 or 2.8.0, whatever
it may be). We could then backport important security fixes to this
branch until February 29, 2012 (same as Geeklog support for 1.7.2). But
what about the next feature branch???
Thoughts?
Rouslan
As far as bumping up the requirement for the next feature release. I
think that it's too early to tell. It will depend on when it will be
ready (few months or few years?) and also on what features we really
need from 1.8.0 (jQuery would probably be awesome)...
Rouslan
This month I'm very busy so I also do not plan to work on new feature
for the forum plugin.
Ben
2011/5/3 Tom <tomh...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "Geeklog Forum" group.
> To post to this group, send email to geeklo...@googlegroups.com.
> To unsubscribe from this group, send email to geeklog-foru...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/geeklog-forum?hl=en.
>
>
Rouslan
I am deleting the words which isn't used from the language files now.
About 200 lines will be able to be deleted.
Therefore, the burden of translation would be reduced a little.
I have some unfinished work.
Few items to be added to the configuration UI remaining in config.php.
This work will not require much time. But, it may not need to meet this release.
dengen
2011/5/4 Rouslan Placella <rou...@placella.com>:
Maybe I should have written a better commit summary...
Rouslan
Ben
2011/5/3 Rouslan Placella <rou...@placella.com>: