Serendipity Forums

Should we have announced that 1.6.1 contains 2k11?

BTW, no biggie, but what happened to giving developers a little heads-up before doing a release?

YL

My fault...I wanted to address the security issues, and was under the impression the 1.6.1 branch was getting no new features or specific things. Sorry!

Regards,
Garvin

I was assuming it had something to do with the security issue, which of course is a priotrity. I was under the impression we'd include 2k11 to get it tested with a broader user base. Maybe we should have guidelines for this kind of stuff?

As I already stated via twitter: no harm done, the included 2k11 version is pretty stable and shouldn't cause any problems. I just would've liked some more time to prepare a blog post.

YL

We'll get the big announcement for 1.7, I promise. )

garvinhicking wrote:We'll get the big announcement for 1.7, I promise. )

Smarty 3?

But seriously (and I know this is another thing on the plate which takes time): maybe we should come up with some short guidelines as to what to put into which branch. Obviously, 2.0 is completely experimental at the moment, but maybe some short "don't do this in the current version branch" or something.

Or is this something PHP coders "just know" and I didn't? Because I wasn't aware that you didn't expect 2k11 to go into 1.6 … (Yes, I might be overthinking this.)

YL

... and I need to get back in the loop. Sorry guys, been so busy, but do want to get more involved.

Hi!

The short idea is this:

Maintenance versions like .1, .2 etc. never get any features that might do anything wrong; even if there's the slightest chance that a feature could break anythinig, it goes into the next release version.

Now to decide what gets into 1.7 and what into 2.0: 1.7 will be our next release, IMHO we should plan it for the end of summer. Smarty3 seems to run pretty stable (great Job, Ian & onli & Co), and we shouldn't stack up too much on branches, so ideally after 1.7 we can move 2.0 to be the master branch.

Once 1.7 is released we'll push the word for more people to check out 2.0 to get more feedback on that, and I hope by then I'll have had the time to checkout 2.0 for myself.

Hope that clears up the idea?

Regards,
Garvin

garvinhicking wrote:even if there's the slightest chance that a feature could break anythinig, it goes into the next release version.

I have to admit I have not "operated" that way concerning 2k11, but the version which is delivered with 1.6.1 should fulfill these requirements. Phew.

garvinhicking wrote:Now to decide what gets into 1.7 and what into 2.0: 1.7 will be our next release, IMHO we should plan it for the end of summer.

Did you just set a rough release date?

As for 2k11, there won't be much to develop there as far as I can see. I have a CSS rewrite in mind, but that's just an option, not a requirement. However, there is the question as to if and when to maybe make it the standard (i.e. preset in any new installation) or default (i.e. fallback) template and how to implement that in a sensible way (think: HTML5 support in core and plugins).

garvinhicking wrote:move 2.0 to be the master branch

Right now, 2.0 is (as far as I understand) primarily the branch for all the work done on the backend. The new backend template is still very much work in progress, so that will take a while.

YL

Yes, 2.0 is just a non-recommended playground for the upcoming new backend based on HTML5, far from being used as is.

Master is 1.7, which still needs some intensive testing and not to forget also some run-down-tweaking btw., as we do not use any of the new Smarty3 features by now. The main converting work is done and it is running pretty stable, but we still might need to wait for a stable Smarty3.2x, which will change some things again... and - did I already say?: have a group of people testing, testing, testing.... reporting, reporting, reporting... to move forward!!! [smile]

I personally would like to have an upgrade doc help kit, to refer what has changed over the years in smarty syntax possibilities, a well done HowTo, how to use nl2br/p and other internals. Even the 2k11 as default will need some changes, as a default is not allowed to have a config (i.e. registerPlugin()), and what about all these remaining feature requests (like http://board.s9y.org/viewtopic.php?f=15 ... #p10430539), or some of the others in "Upcoming Serendipity Features" and so on....

Maybe that points us to run a new thread "upcoming 1.7", gathering feature request, forgotten tweaks and further development...

Sounds like you are going to be pretty busy Ian!!

You are welcome to help!!! [damn blocked BBCode for non colored users!]

Timbalu wrote:how to use nl2br/p

"Don't. Use Textile or Markdown." Done. (Sorry, couldn't resist. )

Timbalu wrote:Even the 2k11 as default will need some changes, as a default is not allowed to have a config

A default template is not allowed to have a config.inc.php? If that's the case and there is no workaround, 2k11 can never become default. It's pretty useless without theme options.

As for feature requests in terms of 2k11, I'm down to two, both not required, but highly recommended:

* "proper" nesting for the categories plugin, i.e. emitting nested categories as a nested list
* we could make better use of new HTML5 elements and/or attributes if some sidebar (and maybe event, not sure) plugins would have an option to emit (X)HTML or HTML5 markup; happy to help with HTML5 markup, but we definitely need a fallback mechanismus for backwards compatibility unless we opt to make a huge break and drop (X)HTML support altogether (I don't think we should do that, but it is an option)

YL

Hi,
Would you happen to have some links to github concerning the actual diffs that represent the security fixes?
Thanks.

Look on https://github.com/s9y/Serendipity/commits/master
just some small escaping to pass-in outgoing links. 2 commits Apr 22, 2012.