Release 2.0.0 - Completed Features (scroll down)

[enricoros]

Release checklist:

• Create a new Release Issue
  • Replace 1.16.0 with the former release, and 2.0.0 with THIS
• Update the Roadmap calling out shipped features
• Create and update a Milestone for the release
  • Assign this task
  • Assign all the shipped roadmap Issues
  • Assign the relevant recently closed Isssues
• Code changes:
  • Search for '2.0.0' and handle those changes
  • Create a release branch 'release-x.y.z': git checkout -b release-2.0.0
  • Create a temporary tag git tag v2.0.0 && git push opensource --tags
  • Create a New Draft GitHub Release, and generate the automated changelog (for new contributors)
  • Update the release version in package.json, and npm i
  • Update the in-app News version number
  • Update in-app News src/apps/news/news.data.tsx
  • Update in-app Cover graphics
  • Update the README.md with the new release
  • Copy the highlights to the docs/changelog.md
• Release:
  • merge onto main git checkout main && git merge --no-ff release-2.0.0
  • re-tag git tag -f v2.0.0 && git push opensource --tags -f
  • verify deployment on Vercel
  • verify container on GitHub Packages
  • update the GitHub release
  • push as stable git push opensource main:main-stable
• Announce:
  • Discord announcement
  • Twitter announcement

Links

• Milestone: https://github.com/enricoros/big-AGI/milestone/X
• GitHub release: https://github.com/enricoros/big-AGI/releases/tag/v2.0.0
• Former release task: #...

Artifacts Generation

You help me generate the following collateral for the new release of my opensource application called big-AGI. The new release is 2.0.0.
To familiarize yourself with the application, the following are the Website and the GitHub README.md.

• paste the URL: https://big-agi.com
• drag & drop: README.md

I am announcing a new version, 2.0.0.
For reference, the following was the collateral for 1.16.0 (Discord announcement, GitHub Release, in-app-news file news.data.tsx).

• paste the former: discord announcement,
• GitHub release,
• news.data.tsx,
• changelog.md

The following are the new developments for 2.0.0:

- ...
- git log --pretty=format:"%h %an %B" v1.16.0..v2.0.0 | clip

• paste the link to the milestone (closed) and each individual issue (content will be downloaded)
• paste the output of the git log command

news.data.tsx

I need the following from you:

1. a table summarizing all the new features in 2.0.0 with the following columns: 4 words description (exactly what it is), short description, usefulness (what it does for the user), significance, link to the issue number (not the commit)), which will be used for the artifacts later
2. then double-check the git log to see if there are any features of significance that are not in the table
3. then score each feature in terms of importance for users (1-10), relative impact of the feature (1-10, where 10 applies to the broadest user base), and novelty and uniqueness (1-10, where 10 is truly unique and novel from what exists already)
4. then improve the table, in decreasing order of importance for features, fixing any detail that's missing, in particular check if there are commits of significance from a user or developer point of view, which are not contained in the table
5. then I want you then to update the news.data.tsx for the new release

release name

please brainstorm 10 different names for this release. see the former names here: https://big-agi.com/blog

You can follow with 'What do you think of Modelmorphic?' or other selected name

cover images

Great, now I need to generate images for this. Before I used the following prompts (2 releases before).

// An image of a capybara sculpted entirely from black cotton candy, set against a minimalist backdrop with splashes of bright, contrasting sparkles. The capybara is using a computer with split screen made of origami, split keyboard and is wearing origami sunglasses with very different split reflections. Split halves are very contrasting. Close up photography, bokeh, white background.
import coverV113 from '../../../public/images/covers/release-cover-v1.13.0.png';
// An image of a capybara sculpted entirely from black cotton candy, set against a minimalist backdrop with splashes of bright, contrasting sparkles. The capybara is calling on a 3D origami old-school pink telephone and the camera is zooming on the telephone. Close up photography, bokeh, white background.
import coverV112 from '../../../public/images/covers/release-cover-v1.12.0.png';

What can I do now as far as images? Give me 4 prompt ideas with the same style as looks as the former, but different scene or action

Readme (and Changelog)

I need you to update the README.md and the with the new release.
Attaching the in-app news, with my language for you to improve on, but keep the tone.

GitHub release

Please create the 2.0.0 Release Notes for GitHub, following the format of the 1.16.0 GitHub release notes attached before.
Use a truthful and honest tone, understanding that people's time and attention span is short.
Today is 2024-XXXX-YYYY.

Now paste-attachment the former release notes (or 1.5.0 which was accurate and great), including the new contributors and
some stats (# of commits, etc.), and roll it for the new release.

Discord announcement

Can you generate my 2.0.0 big-AGI discord announcement from the GitHub Release announcement?
Please keep the formatting and stye of the discord announcement for 1.16.0, but with the new messaging above.

[enricoros]

Pieces of Changelog; work in progress...

User-visible features

• Multimodal
  • Input images
• Multipart
  • Attach documents and images, and both
  • Edit documents (multi-part)
  • Regenerate images, if generated
  • Delete parts
• Costs
  • Show costs and savings on messages and vendors
  • Perfect Anthropic caching support, auto and manual controls
  • Hide past messages in the conversation, to save tokens
• LiveFile on Chrome
  • reload attachments
  • write attachments to disk
  • pair buffers with files
  • (in the making) patch files
  • (in the making) auto-sync attachments (read latest version)
• Data Analyst persona
• Charts support (Data Analyst persona)
• Auto-UI (HTML web UIs)
• Beam: cleanups, +1, (Chat?, Remix?)
• Attach more types, more multi-modal
• Attach web pages: multi-type, with screenshots
• Attach youtube videos with full transcript
• Attach Docx files
• Refer-To multiple user/assistant snippets
• Highlight text in assistant messages
• OpenPipe vendor support: record chats, use your fine-tuned models
• Deepseek vendor support
• Screen capture
• Text Diff app
• Tokenizer app
• Reasoning models support: o1 family, including per-model reasoning_effort setting

Smaller features:

• ReAct: pin the internal monologue box to keep it open
• Fixup Charts code
• Detect max-tokens interruptions, and offer to continue
• Model search box when more than 50
• Notification of chat response completion
• Code: show lines
• Attachments
  • Folders support when drag/drop/paste
• HTML Attachments: cleaner html
• Image Gallery/manager for Draw/Chat
• Better files drop, coexist with mic
• Browsing includes web page screenshots
• PWA: quick voice chat
• OpenRouter: remove non-free models, hide/show all Ability to easily hide all models #605
• Draw app?

Bugfixes:

• [NOT!] Fixed orders of attached files - dragging files from an IDE can result in reordered files
• Microphone: explain errors
• Mac: microphone enablement video
• Mac: cleaner and more usable shortcuts
• no double tap on the persona icon on mobile to edit
• do not remove leading spaces on code (esp. for Anthropic)
• removed Oobabooga support for lack of use

Developers

• tRPC 11
• bug: Stream Link does not abort trpc/trpc#5851
• Audio Generator
• nanoid, indexed
• Dexie for IndexedDB
• reverse proxy instructions
• documented ReAct

Notes

[bradennapier]

Took me a bit to see if you were still active with this project - perhaps a blog update or something if going to be delayed vs saying q4 2024? Love what you've done so far!

[enricoros]

@bradennapier It's going very strong, a dozen commits just this morning. While we'll be releasing a new version on the web by end of month to early access users (but I can't spoil that thunder), opensource devs can use the v2-dev branch in the meantime.

The release had to be pushed to get to the level of quality and scale that's expected from our project. A website redesign is in progress, and will carry updated blogs.