I am +1 for a features freeze. If creating the branch is not going to
prevent us from fixing small bugs then it should be done there.
However, if creating a branch means only fixing the critical issues, then I
think we should wait a little more.
In addition to the regular, extensive testing that we need to do, I think it
would be great if one of our security gurus (Hi Sean!) can somehow clear the
release in that aspect.


Ali B / dmondark
http://www.awhitebox.com


On Tue, Feb 17, 2009 at 7:07 PM, Michael Bishop <[email protected]>wrote:

>
>
>
> On Feb 17, 9:08 am, Scott Merrill <[email protected]> wrote:
> > On Tue, Feb 17, 2009 at 9:00 AM, mikelietz <[email protected]> wrote:
> > > Now that SVN users have been enjoying functioning permissions and a
> > > GUI to manage them, isn't it time for the stable users to see the
> > > fruits of these labors?
> >
> > +1
> >
> > > I realize there's a lot of work involved in a new release (testing,
> > > updating the manual, testing, more testing, etc) but I think more than
> > > anything we need a "OK, we've got enough great new features (working),
> > > it's time to release" consensus.
> >
> > Let's get a coordinated effort to test and document.
> >
> > Is there a specific checklist of things that folks can follow when
> > upgrading or installing any release candidate?
> >
> > Has the ACL stuff been added to the manual at all?
>
> I don't think the manual has been updated in quite some time, as there
> was discussion about going with a different format.  If we want to
> continue using Tiddlywiki, I will see about doing another import from
> the wiki into TW, so we are only adding documentation in one place.
>
> +1 on creating a release branch and going forward with that process.
>
> ~miklb
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to